Method and system for reporting diagnostic trouble code set in vehicle is collision-related

ABSTRACT

A method and computing system for determining whether a DTC set in a vehicle involved in a collision is collision-related or non-collision-related. The method can include determining a vehicle model associated with the vehicle, determining a DTC set within an ECU in the vehicle, determining a damaged portion in the vehicle, determining the DTC is collision-related, and outputting a collision report that indicates the DTC is collision-related. The determined damaged portion indicates where the vehicle was damaged by the collision. Determining the DTC is collision-related can include determining the damaged portion in the vehicle matches a reference vehicle portion associated with both a component attributable to setting the DTC and the vehicle model associated with the damaged vehicle. The collision report can indicate that a different DTC set by the same or a different ECU in the vehicle is non-collision-related.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation application of U.S. patentapplication Ser. No. 16/245,059, filed on Jan. 10, 2019 and published asUnited States Patent Application Publication No. 2020/0223385 A1 on Jul.16, 2020. U.S. patent application Ser. No. 16/245,059 is incorporatedherein by reference.

BACKGROUND

Vehicle collisions are costly. For example, the Illinois Department ofTransportation issued a report in 2015 indicating that there were296,049 crashes involving motor vehicles in Illinois in 2014. That samereport indicates that the total estimated cost of crashes in Illinoisfor 2014 was $5.8 billion. A substantial portion of those costs areassociated with repairing the crashed vehicles (i.e., vehicles involvedin a crash). In some instances, a crashed vehicle will display amalfunction indicator lamp (MIL) to indicate that a diagnostic troublecode (DTC) is currently set to an active status. The DTC can beindicative of a particular vehicle malfunction. Repairing a crashedvehicle can include repairing the vehicle malfunction so that the MIL isnot illuminated when the vehicle owner drives the repaired vehicle awayfrom the repair shop.

In many instances, an insurance company, such as the State Farm MutualAutomobile Insurance Company, issues an insurance policy that covers atleast some of the costs associated with repairing a policy holder'scrashed vehicle. Many insurance policies do not cover the costsassociated with repairing a vehicle malfunction that existed before avehicle crash or a vehicle malfunction that arose while repairing thecrashed vehicle.

Many insurance companies require or determine estimates for repairing acrashed vehicle. A problem in determining an estimate to repair acrashed vehicle is determining whether or not a DTC set to the activestatus within the crashed vehicle existed before the vehicle crash.Existing vehicle scan tools do not determine whether a DTC set in avehicle is collision-related.

Furthermore, in many situations, a vehicle body repair person is skilledin repairing the body of a damaged vehicle, but is unskilled as to usinga vehicle scan tool to diagnose or repair a vehicle because of thecomplexity of the scan tool. A diagnostic tool configured to determineif a DTC is collision-related and/or that is simpler to use would beuseful to many vehicle body repair persons.

OVERVIEW

Several example implementations that relate to diagnosing or repairing avehicle damaged during a collision are described herein. Theimplementations can include determining whether a DTC set in the vehicleis collision-related or non-collision related.

In a first implementation, a method is provided. The method includes:(i) determining, by one or more processors, a vehicle model associatedwith a first vehicle, (ii) determining, by the one or more processors, afirst DTC set within a first electronic control unit (ECU) in the firstvehicle, (iii) determining, by the one or more processors, a firstdamaged portion of the first vehicle, wherein the first damaged portionindicates where the first vehicle was damaged by a collision; (iv)determining, by the one or more processors, the first DTC iscollision-related, wherein determining the first DTC iscollision-related includes determining, by the one or more processors,the first damaged portion of the first vehicle matches a referencevehicle portion associated with both a component attributable to settingthe first DTC and the vehicle model associated with the first vehicle,and (v) outputting, by the one or more processors, a collision reportthat indicates the first DTC is collision-related.

In a second implementation, a computing system is provided. Thecomputing system includes (a) a computer-readable memory having storedthereon a reference vehicle portion associated with both a componentattributable to setting a first DTC and a vehicle model associated witha first vehicle, and (b) one or more processors configured to refer tothe computer-readable memory. The one or more processors is programmedto: (a) determine the vehicle model associated with the first vehicle;(b) determine the first DTC set within a first ECU in the first vehicle;(c) determine, a first damaged portion of the first vehicle, wherein thefirst damaged portion indicates where the first vehicle was damaged by acollision; (d) determine the first DTC is collision-related, whereindetermining the first DTC is collision-related includes determining thefirst damaged portion of the first vehicle matches the reference vehicleportion associated with both the component attributable to setting thefirst DTC and the vehicle model associated with the first vehicle; and(e) output a collision report that indicates the first DTC iscollision-related.

In a third implementation, a computer readable memory is provided. Thecomputer readable memory has stored thereon instructions executable byone or more processors to cause a computing system to perform functions.The functions include (a) determining a vehicle model associated with afirst vehicle; (b) determining a first DTC set within a first ECU in thefirst vehicle; (c) determining a first damaged portion of the firstvehicle, wherein the first damaged portion indicates where the firstvehicle was damaged by a collision; (d) determining the first DTC iscollision-related, wherein determining the first DTC iscollision-related includes determining, by the one or more processors,the first damaged portion of the first vehicle matches a referencevehicle portion associated with both a component attributable to settingthe first DTC and the vehicle model associated with the first vehicle;and (e) outputting a collision report that indicates the first DTC iscollision-related.

Other implementations will become apparent to those of ordinary skill inthe art by reading the following detailed description, with referencewhere appropriate to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a diagram showing a vehicle in accordance with the exampleimplementations.

FIG. 1B is a diagram showing an operating environment in which theexample implementations can operate.

FIG. 2 is a diagram showing an operating environment in which theexample implementations can operate.

FIG. 3A is a simple block diagram of a scanner in accordance with theexample implementations.

FIGS. 3B and 3C show memory content of a scanner in accordance withexample implementations.

FIG. 3D is a diagram showing example crash and damage data in accordancewith example implementations.

FIG. 4A is a simple block diagram of a server in accordance with theexample implementations.

FIG. 4B is a diagram showing example crash and damage data in accordancewith example implementations.

FIG. 5A is a flowchart depicting a set of functions that can be carriedout in accordance with the example implementations.

FIG. 5B is a graph illustrating parameter value comparisons inaccordance with the example implementations.

FIGS. 6A, 6B, 7A, 7B, 8A, 8B, 9A, 9B, 10A, 10B, 11A, 11B, 12A, 12B, 13A,13B, 14A, 14B, 15A, 15B, 15C, 15D, 15E, 15F, 15G, 15H, 15I, 15J, 15K,15L, 15M, 15N, 15O, and 15P depict example implementations of thescanner and a display screen shown on a display of the scanner inaccordance with the example implementations.

FIG. 15Q is a diagram depicting example touch screen display inputs inaccordance with the example implementations.

FIGS. 16A and 16B are diagrams showing example vehicle reference data inaccordance with the example implementations.

FIG. 17 is a diagram showing an example collision report in accordancewith the example implementations.

FIG. 18A is another flowchart depicting a set of functions that can becarried out in accordance with the example implementations.

FIGS. 18B and 18C depict example implementations of the scanner and adisplay screen shown on a display of the scanner in accordance with theexample implementations.

FIG. 19 is a simple block diagram of a computing system in accordancewith the example implementations.

FIG. 20 is a schematic illustrating a conceptual partial view of anexample computer program product.

DETAILED DESCRIPTION I. Introduction

In this description, a vehicle damaged during and/or due to a collisionis at least sometimes referred to as a “damaged vehicle,” and a vehiclethat is inoperative or that is operative, but exhibiting some fault, isat least sometime referred to as a “malfunctioning vehicle.” Amalfunctioning vehicle can, but need not necessarily, be a damagedvehicle. In at least some instances, one or more of the faults of themalfunctioning vehicle is due to the vehicle being damaged during acollision. In those or in other instances, one or more of the faults ofmalfunctioning vehicle is not due to the vehicle being damaged in acollision.

In general, this description pertains to vehicle scanner technologyand/or to computing systems configured to perform unconventionalfunctions with respect to a vehicle, such as a damaged vehicle and/or amalfunctioning vehicle. More particularly, at least a portion of thisdescription pertains to a damaged vehicle, and/or to a computing system(e.g., a vehicle scan tool and/or a server) configured to performunconventional functions with respect to the damaged vehicle. Thecomputing systems described herein can also be used on or with respectto vehicles that have not been damaged due to a collision and that arenot exhibiting any fault.

As noted above, a vehicle scan tool is an example of a computing systemof the example implementations. A vehicle scan tool (or more simply, a“scanner”) is a computing system that is operatively and removablyconnectable to a vehicle in order to communicate with one or morevehicle components on the vehicle. A vehicle scan tool is not a vehiclecomponent, but can be removably connected to a vehicle component, suchas an on-board diagnostic connector, and can communicate with a vehiclecomponent, such as an electronic control unit, using vehicle datamessages. The scanner can include a vehicle communication transceiver totransmit vehicle data messages to a vehicle and/or to receive vehicledata messages from a vehicle.

In an example implementation, a scanner can be configured to perform oneor more unconventional functions, such as determining whether a DTC setin a vehicle is collision-related and/or determining possible relatedcollision damage (PRCD) to the vehicle based on point-of-impact (POI)damage to the vehicle. In that or another example implementation, thescanner provides the server with information the server uses todetermine whether the DTC is collision-related. In those or anotherexample implementation, the scanner and/or the vehicle including the ECUthat set the DTC provides the server with information the server uses todetermine whether the DTC is collision-related. The scanner and/or theserver can determine whether a DTC is non-collision related. A DTC thatis collision-related or non-collision related can have a status ofcurrent, pending, history, or some other status.

In the prior mentioned example implementations and/or another exampleimplementation, the scanner and/or a server determines PRCD to a damagedvehicle. The vehicle damage determined to be PRCD can include vehicledamage overlooked by a person (e.g., an inspector) inspecting a vehiclefor collision damage. Typically, the POI damage is readily visible tothe inspector, but the PRCD is not readily visible to the inspector. Insome instances, the PRCD is visible, but only after removing one or moreother vehicle components. In these example implementations, the scannerand/or the server can include a processor configured to determine thePRCD and/or a user interface that shows the determined PRCD. The userinterface can be configured to allow a user to select the PRCD so as tocause a processor to augment a collision report based on the PRCD. Thedetermined PRCD can, but need not necessarily, include text and/or animage representative of vehicle damage to a vehicle.

In any of the aforementioned example implementations, the scanner can beconfigured to adjust a vehicle that is connected to scanner. Theadjustment performed by the scanner can, for example, include resettinga vehicle component, initializing a vehicle component, calibrating avehicle component, or programming a vehicle component. Resetting avehicle component can include powering the component off and back on.Programming a vehicle component can include programming the vehiclecomponent for the first time or reprogramming a vehicle component thatwas programmed previously.

Reprogramming a vehicle component can include deleting a portion of anexisting program from the vehicle component prior to writing a newprogram into the vehicle component. Calibrating a vehicle component caninclude writing calibration values into a portion of a memory in thevehicle component, the calibration values may be referred to by anexecutable program executed by a processor in the vehicle component.Initializing a vehicle component can include setting the vehiclecomponent to a particular state, such as a window controller in thewindow fully-up state or the window fully-down state.

II. Example Vehicle and Operating Environment

FIG. 1A shows a vehicle 1. A vehicle, such as the vehicle 1, is a mobilemachine that can be used to transport a person, people, or cargo. Avehicle can be driven or otherwise guided along a path (e.g., a pavedroad or otherwise) on land, in water, or in the air or outer space. Avehicle can be wheeled, tracked, railed, or skied. A vehicle can beguided by a user within the vehicle or by a user outside of the vehicleby use of a remote control. A vehicle can be guided at least partiallyautonomously. In the case of an autonomous vehicle, the vehicle can atleast sometimes be guided along a path without any person or cargoinside or on the vehicle. A vehicle can include an automobile, amotorcycle, an all-terrain vehicle (ATV) defined by ANSI/SVIA-1-2007, asnowmobile, a personal watercraft (e.g., a JET SKI® personalwatercraft), a light-duty truck, a medium-duty truck, a heavy-dutytruck, a semi-tractor, a farm machine, a van (such as a dry orrefrigerated van), a tank trailer, a platform trailer, or an automobilecarrier. A vehicle can include or use any appropriate voltage or currentsource, such as a battery, an alternator, a fuel cell, and the like. Avehicle can include or use any desired drive system or engine. Thatdrive system or engine can include items that use fossil fuels, such asgasoline, natural gas, propane, and the like, electricity, such as thatgenerated by a battery, magneto, fuel cell, solar cell and the like,wind and hybrids or combinations thereof. A vehicle can include anelectronic control unit (ECU) 3, a data link connector (DLC) 2, and avehicle communication link 4 that operatively connects the DLC 2 to theECU 3. The ECU 3 can detect a malfunction in the vehicle and set a DTCindicative of the malfunction to an active status.

A vehicle manufacturer can build various quantities of vehicles eachcalendar year (i.e., January 1^(st) to December 31^(st)). Some vehiclemanufacturers build one vehicle model or multiple different vehiclemodels. In some instances, a vehicle manufacturer defines a model yearfor a particular vehicle model to be built. The model year can start ona date other than January 1^(st) and/or can end on a date other thanDecember 31^(st). The model year can span portions of two or morecalendar years. Two or more different vehicle models built by a vehiclemanufacturer during a particular calendar year can have the same ordifferent defined model years. The vehicle manufacturer can buildvehicles of a vehicle model with different vehicle options. For example,a particular vehicle model can include vehicles with six-cylinderengines and vehicles with eight-cylinder engines. The vehiclemanufacturer or another entity can define vehicle identifyinginformation for each vehicle model built by the vehicle manufacturer.Particular vehicle identifying information identifies particular sets ofvehicles (e.g., all vehicles of a particular vehicle model for aparticular vehicle model year or all vehicles of a particular vehiclemodel for a particular vehicle model year with a particular set of oneor more vehicle options).

As an example, the particular vehicle identifying information caninclude indicators of characteristics of the vehicle such as when thevehicle was built (e.g., a vehicle model year), who built the vehicle(e.g., a vehicle make (i.e., vehicle manufacturer)), marketing namesassociated with vehicle (e.g., a vehicle model name), and features ofthe vehicle (e.g., an engine type). In accordance with that example, theparticular vehicle identifying information can be referred to by anabbreviation YMME or Y/M/M/E, where each letter in the order shownrepresents a model year identifier, vehicle make identifier, vehiclemodel name identifier, and engine type identifier, respectively, or anabbreviation YMM or Y/M/M, where each letter in the order shownrepresents a model year identifier, vehicle make identifier, and vehiclemodel name identifier, respectively. An example Y/M/M/E is2004/Toyota/Camry/4Cyl, in which “2004” represents the model year thevehicle was built, “Toyota” represents the name of the vehiclemanufacturer Toyota Motor Corporation, Aichi Japan, “Camry” represents avehicle model name built by that manufacturer, and “4Cyl” represents anengine type a four cylinder internal combustion engine (ICE)) within thevehicle. A person skilled in the art will understand that other featuresin addition to or as an alternative to “engine type” can be used toidentify a vehicle model using particular vehicle identifyinginformation, and for some purposes, a vehicle model could be identifiedby its vehicle make and vehicle model name M/M. These other features canbe identified in various manners, such as a regular production option(RPO) code, such as the RPO codes defined by the General Motors CompanyLLC, Detroit Mich. Furthermore, the vehicle identifying information canbe combined and displayed as a vehicle identification number (VIN). TheVIN can be displayed on a VIN label.

The vehicle communication link 4 within the vehicle 1 can include one ormore conductors (e.g., copper wire conductors) or can be wireless. As anexample, the vehicle communication link 4 can include one or moreconductors for carrying vehicle data messages in accordance with avehicle data message (VDM) protocol. A VDM protocol can include aSociety of Automotive Engineers (SAE)® J1850 (PWM or VPW) VDM protocol,an International Organization of Standardization (ISO)® 15764-4controller area network (CAN) VDM protocol, an ISO® 9141-2 K-Line VDMprotocol, an ISO® 14230-4 KWP2000 K-Line VDM protocol, an ISO® 17458(e.g., parts 1-5) FlexRay VDM protocol, an ISO® 17987 local interconnectnetwork (LIN) VDM protocol, a MOST® Cooperation VDM protocol (such asthe MOST Specification Rev. 3.0 E2, or the MOST® Dynamic Specification,Rev. 3.0.2), or some other VDM protocol defined for performingcommunications with or within the vehicle 1. Each and every VDMdiscussed in this description is arranged according to a VDM protocol.The vehicle communication link 4 can be connected to one or more ECU 3and to the DLC 2.

The ECU 3 can control various aspects of vehicle operation or componentswithin a vehicle. For example, the ECU 3 can include a powertrain (PT)system ECU, an engine control module (ECM) ECU, a powertrain controlmodule (PCM) ECU, a supplemental inflatable restraint (SIR) system(i.e., an air bag system) ECU, an entertainment system ECU, or someother ECU. The ECU 3 can receive inputs (e.g., a sensor input), controloutput devices (e.g., a solenoid), generate a vehicle data message (VDM)(such as a VDM based on a received input or a controlled output), andset a diagnostic trouble code (DTC) as being active or history for adetected fault or failure condition within a vehicle. The ECU 3 canperform a functional test or a reset procedure in response to receivinga VDM requesting performance of the functional test or the resetprocedure. A VDM received by the ECU 3 can include a parameter requestthat includes a parameter identifier (PID). A VDM transmitted by the ECU3 can include a response including the PID and a PID data value for thePID. The ECU 3 can be connected to a vehicle component 5, such as avehicle battery, a sensor, a vehicle chassis, a solenoid, a fuelinjector, a fuel pump, or some other vehicle component via a circuit 6.The SIR system can include one or more initiators (sometimes referred toas “squibs”) for each air bag in the vehicle. The squibs can includeelectrical circuitry upon which the SIR ECU can performself-diagnostics. The SIR ECU can output an electrical current to asquib to initiate deployment of an air bag of the SIR system.

The DLC 2 can include a connector such as an on-board diagnostics (OBD)I connector, an OBD II connector, or some other connector. An OBD IIconnector can include slots for retaining up to sixteen connectorterminals, but can include a different number of slots or no slots atall. As an example, the DLC 2 can include an OBD II connector that meetsthe SAE J1962 specification such as a connector 16M, part number12110252, available from Aptiv LLC of Dublin, Ireland. The DLC 2 caninclude conductor terminals that connect to a conductor in the vehicle1. For instance, the DLC 2 can include connector terminals that connectto conductors that respectively connect to positive and negativeterminals of a vehicle battery. The DLC 2 can include one or moreconductor terminals that connect to a conductor of the vehiclecommunication link 4 such that the DLC 2 is operatively connected to theECU 3.

Many vehicles require unlocking or engaging some component before thevehicle can be driven or guided along the path. For example, somevehicles that include an ICE and a starter motor require unlocking a keycylinder with a key in order to engage the starter motor to start theICE. In some instances, the starter motor can be engaged by pushing apush button while also pushing a brake pedal in the vehicle. Somevehicles, such as an electric vehicle, may or may not include an ICE,but still require use of a key or push button before the vehicle can bedriven or guided along the path. Moreover, some other vehicles providefor starting a vehicle by bringing a key fob in proximity to the vehicleand positioning a transmission direction selector in a forward orreverse position. Upon starting such vehicles, the vehicles can bedriven or guided along a path. Other examples configurations forstarting a vehicle are also available.

Each instance of driving or guiding a vehicle along a path is a “drivecycle.” For a vehicle that requires a key to start the ICE, the drivecycle can further be defined with respect to the time from when the keyis used to start the ICE until such time that the key is used to stopthe ICE. For vehicles that require a key to start the ICE, the drivecycle can be referred to as “key cycle.” Furthermore, some vehiclestrack “warm-up cycles,” where each warm-up cycle is achieved if anoperating temperature of the vehicle reaches at least a thresholdtemperature since a current drive cycle began.

Next, FIG. 1B is a diagram showing an operating environment 7 in whichthe example implementations can operate. The operating environment 7includes the vehicle 1, a scanner 8, a server 9, a vehicle communicationlink (VCL) 10, and a network 11. FIG. 1B shows that the vehicle 1 hasbeen in a collision. The right side of the vehicle's front end sustaineddamage during the collision.

The VCL 10 is configured to carry communications between the vehicle 1and the scanner 8. The VCL 10 can carry other communications, such ascommunications between the vehicle 1 and one or more other computingsystems operatively connected to the VCL 10, communications between thescanner 8 and one or more other computing systems operatively connectedto the VCL 10, or communications between two or more devices other thanthe vehicle 1 and the scanner 8.

The network 11 is configured to carry communications between the scanner8 and the server 9. The network 11 can carry other communications, suchas communications between the scanner 8 and one or more other computingsystems operatively connected to the network 11, communications betweenthe server 9 and one or more other computing systems operativelyconnected to the network 11, or communications between two or moredevices other than the scanner 8 and the server 9. The network 11 caninclude various network components such as switches, modems, gateways,antennas, cables, transmitters, or receivers. The network 11 can includea wide area network (WAN). The WAN can carry data using packet-switchedor circuit-switched technologies. The WAN can include an air interfaceor wire to carry the data. The network 11 can include a network or atleast a portion of a network that carries out communications using aTransmission Control Protocol (TCP) and the Internet Protocol (IP), suchas the communication network commonly referred to as the Internet.

Next, FIG. 2 is a diagram showing an operating environment 12 in whichthe example implementations can operate. The operating environment 12includes aspects of the operating environment 7. The operatingenvironment 12 also includes repair shop 13, 14, 15, 16, a collisionservices provider 17, and insurance companies 18, 19, and 20. The repairshop 13, 14, 15, 16 include a scanner 8, 21, 22, 23, respectively. Therepair shop 13, 14, 15, 16 are business entities at which techniciansrepair vehicles. The repairs performed at the repair shop 13, 14, 15, 16can include any of a variety of repairs, such as vehicle body repairs,mechanical repairs, electrical repairs, vehicle maintenance, etc.

Some repair shops are large and can accommodate a large number ofvehicles at any given time, whereas some repair shops are small and canaccommodate a small number of vehicles at any given time. The repairshop 13 is shown with the vehicle 1 and a vehicle 27. The repair shop 14is shown with vehicle 28, 29. The repair shop 15 is shown with vehicle30, 31. The repair shop 16 is shown with vehicle 32, 33. Since therepair shop 13, 14, 15, 16 are example repair shops a person skilled inthe art will understand that a different number of vehicles could be ator within one or more of the repair shop 13, 14, 15, 16. A repair shopcan include more than one scanner.

The insurance company 18, 19, 20 includes network computing system (NCS)24, 25, 26, respectively, operatively connected to the network 11. TheNCS 24, 25, 26 can include network transceivers for receiving acommunication from another device connected to the network 11, such asthe scanner 8, 21, 22, 23, or the server 9. The communication receivedby the insurance company 18, 19, 20 can include a collision reportoutput by a scanner, such as scanner 8, 21, 22, 23, or by the server 9.The collision services provider 17 includes the server 9. The collisionservices provider 17 can, for example, include a business entity thatprovides repair information to repair shops. The collision servicesprovider 17 can operate the server 9 to receive repair orders regardinginstances of vehicles being serviced and determine from the repairorders characteristics regarding different vehicle models, such aswhether or not a DTC is commonly or rarely set in the vehicle models.FIG. 2 shows an implementation in which the repair shop 13, 14, 15, 16,the collision services provider 17, and the insurance company 18, 19, 20include computing systems operatively connected to the network 11.

III. Example Computing Systems

A. Example Scanner

Next, FIG. 3A is a simple block diagram of the scanner 8, in accordancewith example implementations. The scanner 8 can include one or more ofthe following: a processor 40, a network transceiver 41, a vehiclecommunication transceiver 42, a display 43, a keypad, 44, a capturedevice 45, an audio device 46, or a memory 47. Two or more of thosecomponents can be operatively connected via a system bus, network, orother connection mechanism 50. The scanner 8 can also include a powersupply 48 and/or a housing 49. The scanner 21, 22, 23 can be configuredlike any implementation of the scanner 8.

1. Processor

A processor, such as the processor 40 or any other processor discussedin this description (e.g., a processor 440 shown in FIG. 4A), caninclude one or more processors. A processor can include a generalpurpose processor (e.g., an INTEL® single core microprocessor or anINTEL® multicore microprocessor), or a special purpose processor (e.g.,a digital signal processor, a graphics processor, an embedded processor,or an application specific integrated circuit (ASIC) processor). Aprocessor can be configured to execute computer-readable programinstructions (CRPI). The CRPI discussed in this disclosure, such as theCRPI 60, 460, can include assembler instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, and/or either source code or object code written inone or any combination of two or more programming languages. As anexample, a programming language can include an object orientedprogramming language such as Java, Python, or C++, or a conventionalprocedural programming language, such as the “C” programming language. Aprocessor can be configured to execute hard-coded functionality inaddition to or as an alternative to software-coded functionality (e.g.,via CRPI). The processor 40 can be programmed to perform any function orcombination of functions described herein as being performed by thescanner 8. Anything that a processor receives or transmits, such asdata, can, but need not necessarily, be arranged as computer-readabledata.

An embedded processor refers to a processor with a dedicated function orfunctions within a larger electronic, mechanical, pneumatic, and/orhydraulic device, and is contrasted with a general purpose computer. Theembedded processor can include a central processing unit chip used in asystem that is not a general-purpose workstation, laptop, or desktopcomputer. In some implementations, the embedded processor can execute anoperating system, such as a real-time operating system (RTOS). As anexample, the RTOS can include the SMX® RTOS developed by Micro Digital,Inc., such that the processor 40, 440 can, but need not necessarily,include (a) an advanced RISC (reduced instruction set computer) machine(ARM) processor (e.g., an AT91SAM4E ARM processor provided by the AtmelCorporation, San Jose, Calif.), or (b) a COLDFIRE® processor (e.g., a52259 processor) provided by NXP Semiconductors N.V., Eindhoven,Netherlands. A general purpose processor, a special purpose processor,and/or an embedded processor can perform analog signal processing and/ordigital signal processing.

2. Memory

A memory, such as the memory 47 or any other memory discussed in thisdescription (e.g., a memory 446 shown in FIG. 4A), can include one ormore memories. Any memory discussed in this description can thus bereferred to as least one memory or one or more memories. A memory caninclude a non-transitory memory, a transitory memory, or both anon-transitory memory and a transitory memory. A non-transitory memory,or a portion thereof, can be located within or as part of a processor(e.g., within a single integrated circuit chip). A non-transitorymemory, or a portion thereof, can be separate and distinct from aprocessor.

A non-transitory memory can include a volatile or non-volatile storagecomponent, such as an optical, magnetic, organic or other memory or discstorage component. Additionally or alternatively, a non-transitorymemory can include or be configured as a random-access memory (RAM), aread-only memory (ROM), a programmable read-only memory (PROM), anerasable programmable read-only memory (EPROM), an electrically erasableprogrammable read-only memory (EEPROM), or a compact disk read-onlymemory (CD-ROM). The RAM can include static RAM or dynamic RAM.

A transitory memory can include, for example, CRPI provided over acommunication link, such as the network 11. The network 11 can include adigital or analog communication link. The network 11 can include a wiredcommunication link including one or more wires or conductors, or awireless communication link including an air interface.

A “memory” can be referred to by other terms such as a“computer-readable memory,” a “computer-readable medium,” a“computer-readable storage medium,” a “data storage device,” a “memorydevice,” “computer-readable media,” a “computer-readable database,” “atleast one computer-readable medium,” “one or more computer-readablemedium,” and/or a “system memory.” Any of those alternative terms can bepreceded by the prefix “transitory” if the memory is transitory or“non-transitory” if the memory is non-transitory. For a memory includingmultiple memories, two or more of the multiple memories can be the sametype of memory or different types of memories.

3. Transceivers

A network transceiver, such as the network transceiver 41 or any othernetwork transceiver discussed in this description (e.g., the networktransceiver 441 shown in FIG. 4A), can include one or more networktransceivers. Each network transceiver includes one or more transmittersconfigured to transmit data or a communication onto a network, such asthe network 11. The network transceiver 41 can transmit any data orcommunication discussed as being transmitted, output, or provided by thescanner 8 to one or more of the following: the server 9, the NCS 24, 25,26, the collision service provider 17, or the insurance company 18, 19,20. Each network transceiver (e.g., the network transceiver 41, 441)includes one or more receivers configured to receive data or acommunication carried over a network, such as the network 11. Thenetwork transceiver 41 can receive any data or communications discussedas being received by the scanner 8 or the network transceiver 41 fromone or more of the following: the server 9, the NCS 24, 25, 26, thecollision service provider 17, or the insurance company 18, 19, 20. Thenetwork transceiver 41 can transmit a collision report 68 to one or moreof the following: the server 9, the NCS 24, 25, 26, the collisionservice provider 17, or the insurance company 18, 19, 20.

The VCT 42 includes a transceiver configured for transmitting a VDM tothe vehicle 1 via the VCL 10 and for receiving a VDM transmitted by thevehicle 1 via the VCL 10. The VCT 42 can include a transceiver (e.g., anintegrated transmitter and receiver, or a distinct transmitter and adistinct receiver). In some implementations, a transmitter of the VCT 42can be configured to transmit a VDM to the vehicle 1 via the VCL 10. TheVDM transmitted to the vehicle 1 via the VCL 10 can include a requestfor diagnostic information (such as a DTC) from the ECU 3. In thoseimplementations, the receiver of the VCT 42 can be configured to receivea VDM transmitted by the vehicle 1 over the VCL 10. The VDM received bythe receiver of the VCT via the VCL 10 can include diagnosticinformation transmitted by the ECU 3. A VDM can include a componentidentifier, such as an identifier of the ECU 3 that transmits the VDM.The VDM can include data indicative of a DTC set by the ECU 3. Theprocessor 40 can select data from within the VDM and cause the selecteddata to be displayed by the display 43.

The VCT 42 can include a transceiver (e.g., an integrated transmitterand receiver, or a distinct transmitter and a distinct receiver). Thetransmitter of the VCT 42 can be configured to transmit a VDM to avehicle or, in particular, an ECU within the vehicle. The VDMtransmitted by the VCT 42 can include a VDM with a request for a DTC setby the ECU. The receiver of the VCT 42 can be configured to receive aVDM transmitted by an ECU over the VCL 10. The VDM received by the VCT42 can include an OBD II VDM indicative of a DTC set within the vehicle.As an example, a wired transceiver of the VCT 42 can include atransceiver such as a system basis chip with high speed CAN transceiver33989 provided by NXP Semiconductors, Eindhoven, Netherlands.

The VCT 42 can include and/or be connected to a wiring harness. Thewiring harness can be configured to provide a wired connection betweenthe scanner 8 and the vehicle 1, in particular, an ECU in the vehiclestoring crash data. In some implementations, the wiring harness isremovably connectable to the DLC 2 within the vehicle 1. In thoseimplementations, the DLC 2 can provide the scanner 8 with an indirectconnection to the ECU that stores crash data. In some otherimplementations, the wiring harness is directly connectable to both thescanner 8 and the ECU that stores crash data. The VCT 42 can includeand/or connect to one or more connectors, one of which can be located atthe end of the wiring harness.

The VCT 42 can include a wireless transceiver to communicate with aseparate wireless transceiver within the scanner 8. A transmitter, suchas a transmitter in the network transceiver 41 or 441 or in the VCT 42,can transmit radio signals carrying data or a communication, and areceiver, such as a receiver in the network transceiver 41 or 441 or inthe VCT 42, can receive radio signals carrying data or a communication.A transceiver with a radio transmitter and radio receiver can includeone or more antennas and can be referred to as a “radio transceiver,” an“RF transceiver,” or a “wireless transceiver.”

A radio signal transmitted or received by a radio transceiver can bearranged in accordance with one or more wireless communication standardsor protocols such as an Institute of Electrical and ElectronicsEngineers (IEEE) standard, such as (i) an IEEE 802.11 standard forwireless local area networks (wireless LAN) (which is sometimes referredto as a Wi-Fi standard) (e.g., 802.11a, 802.11b, 802.11g, or 802.11n),(ii) an IEEE 802.15 standard (e.g., 802.15.1, 802.15.3, 802.15.4(ZigBee), or 802.15.5) for wireless personal area networks (PANs), (iii)a Bluetooth version 4.1 or 4.2 standard developed by the BluetoothSpecial Interest Group (SIG) of Kirkland, Wash., (iv) a cellularwireless communication standard such as a long term evolution (LTE)standard, (v) a code division multiple access (CDMA) standard, (vi) anintegrated digital enhanced network (IDEN) standard, (vii) a globalsystem for mobile communications (GSM) standard, (viii) a general packetradio service (GPRS) standard, (ix) a universal mobiletelecommunications system (UMTS) standard, (x) an enhanced data ratesfor GSM evolution (EDGE) standard, (xi) a multichannel multipointdistribution service (MMDS) standard, (xii) an InternationalTelecommunication Union (ITU) standard, such as the ITU-T G.9959standard referred to as the Z-Wave standard, (xiii) a 6LoWPAN standard,(xiv) a Thread networking protocol, (xv) an International Organizationfor Standardization (ISO/International Electrotechnical Commission (IEC)standard such as the ISO/IEC 18000-3 standard for Near FieldCommunication (NFC), (xvi) the Sigfox communication standard, (xvii) theNeul communication standard, or (xviii) the LoRaWAN communicationstandard. Other examples of the wireless communication standards orprotocols are available.

Additionally or alternatively, a transmitter, such as a transmitter inthe network transceiver 41 or 441 or in the VCT 42, can transmit asignal (e.g., one or more signals or one or more electrical waves)carrying or representing data or a communication onto a wire (e.g., oneor more wires) and a receiver, such as a receiver in the networktransceiver 41 or 441 or in the VCT 42, can receive via a wire a signalcarrying or representing data or a communication over the wire. The wirecan be part of a network, such as the network 11. The signal carriedover a wire can be arranged in accordance with a wired communicationstandard such as a Transmission Control Protocol/Internet Protocol(TCP/IP), an IEEE 802.3 Ethernet communication standard for a LAN, adata over cable service interface specification (DOCSIS standard), suchas DOCSIS 3.1, a USB specification (as previously described), or someother wired communication standard.

The data or communication transmitted by a network transceiver, such asthe network transceiver 41 or 441, can include a destination identifieror address of a network device to which the data or communication is tobe transmitted. The data or communication transmitted by a networktransceiver can include a source identifier or address of the systemcomponent including the network transceiver. The source identifier oraddress can be used to send a response to the network device thatincludes the network transceiver that sent the data or communication.

A network transceiver that is configured to carry out communicationsover the network 11, such as the network transceiver 41 or 441, caninclude one or more of the following: a modem, a network interface card,or a chip mountable on a circuit board. As an example the chip caninclude a CC3100 Wi-Fi® network processor available from TexasInstruments, Dallas, Tex., a CC256MODx Bluetooth® Host ControllerInterface (HCI) module available from Texas instruments, or a differentchip for communicating via Wi-Fi®, Bluetooth® or another communicationprotocol.

A device within or coupled to the network 11 or that communicates viathe network 11 using a packet-switched technology can be locallyconfigured for a next ‘hop’ in the network (e.g., a device or addresswhere to send data to, and where to expect data from). As an example, adevice (e.g., a transceiver) configured for communicating using an IEEE802.11 standard can be configured with a network name, a networksecurity type, and a password. Some devices auto-negotiate thisinformation through a discovery mechanism (e.g., a cellular phonetechnology).

The scanner 8 can also include a communication interface 667, a networkcontroller 668, and a communication port 669, as shown in FIG. 19.

4. User Interface Components

One or more components of the scanner 8 can be referred to as a “userinterface component.” As an example, the display 43, the keypad 44, thecapture device 45, and/or the audio device 46 can be referred to as auser interface component. A user interface component can include acontrol. A control can be used by a user of the scanner 8 to enter aninput into the scanner 8, such as an input detectable by the processor40. A control can include a virtual control of a display screen shown onthe display 43. A control can include a hardware control, such as a keyof the keypad 44. In one respect, a virtual control can be independentof the keys of the keypad 44. In that case, an input can be enteredusing the virtual control by use of the display 43, for example bytouching the display 43 in proximity to the virtual control. In anotherrespect, a virtual control shown on the display 43 can be associatedwith a key of the keypad 44. In that case, an input can be entered usingthe virtual control by use of the key of the keypad 44. The keypad 44can include a key that is not associated with a virtual control shown onthe display. Moreover, the keypad 44 can include a key that isassociated with a virtual control of some display screen and that is notassociated with a virtual control on one or more other display screens.

The display 43 can, but need not necessarily, include a capacitive touchscreen display, a resistive touch screen display, a plasma display, alight emitting diode (LED) display, a cathode ray tube display, anorganic light-emitting diode (OLED) display, or a liquid crystal display(LCD). An OLED display can include an active-matrix OLED or apassive-matrix OLED. The LCD can be backlit, color LCD. The display 43can include a touch screen display with the LCD. For instance, thedisplay 43 can include a capacitive (such as a projective capacitive)touch screen display or a resistive touch screen display. Other examplesof the display 43 are available.

The display 43 can include a horizontal scroll bar and a vertical scrollbar. The horizontal scroll bar and the vertical scroll bar can be usedto cause the display 43 to display a non-visible portion of an image ora display screen output by the processor 40, 440 to be displayed. Thedisplay 43 can display still images, such as a still image of a vehicle.The display 43 can display videos, such as a video with contentregarding a warning or procedure pertaining to repairing a vehicledamaged by a collision. The display 43 can display text, such as textwith content regarding a warning or procedure pertaining to repairing avehicle damaged by a collision.

The display 43 can display (e.g., present visually) a display screenthat includes graphical objects. For instance, the display screen canshow virtual controls via which a user can enter an input pertaining touse of the scanner 8. The input can represent a selection and/orinformation. As an example, a virtual control can include a graphicalbutton, such as a rectangle surrounding text representative of aselection or information associated with the button. As another example,a virtual control can include a pull-down menu, a check box, and/or atext box for entering textual information. A virtual control configuredfor entering a selection can be referred to as a “selector.” The displayscreen can, for example, show any of the content shown in FIG. 6A toFIG. 15N. Other examples of content displayable by the display 43 areavailable. The processor 40 can output a display screen to the display43. The display screen, output by the processor 40, can be referred toas a “display output.”

The keypad 44 can include one or more components configured for use by auser to enter selections or information into the scanner 8. A keyconfigured for entering a selection can be referred to as a selector.The keypad 44 can include one or more control keys, or more simply“key”. A key can include a push button, such as a press-and-hold buttonor a press-and-release button. In some implementations, the keypad 44includes a hardware keypad with a set of numeric keys, alpha-numerickeys, alphabet keys, or some other hardware keys. In some otherimplementations, the display 43 includes at least a portion of thekeypad 44 that includes soft keys, such as capacitive or resistive keysof a touch screen display. In still other implementations, the keypadincludes one or more hardware keys, such as a power on/off key, a yeskey and a no key, or four direction keys for selecting a direction suchas up, down, left or right. In still yet other implementations, the softkeys of the keypad 44 on the touch screen display can include a poweron/off key, a yes key and a no key, or four direction keys.

Example keys of the keypad 44 are shown in FIG. 6A. The keypad 44 can beused to enter a variety of information into the processor 40. As anexample, the information entered by the keypad 44 can include one ormore of the following: vehicle model information, a damaged portionindicating where a vehicle sustained damage during a collision, orinsurance company information so that the processor 40 can transmit acollision report to an insurance company. The vehicle model informationcan include a vehicle model identifier or one or more vehicle modelattributes that can be used to determine a vehicle model. The display 43can display the vehicle model identifier (such as a vehicle modelidentifier 179 shown in FIG. 11A or a vehicle model identifier 320 shownin at least FIG. 15G).

The capture device 45 includes one or more components configured togenerate data based on objects in proximity to the scanner 8 and/orsignals from which that data can be generated. As an example, the datagenerated by the capture device 45 can include an image (e.g., an imagefile), content of a scanned image, and/or measurement data. In at leastsome implementations, the capture device 45 includes one or more of thefollowing: an image scanner, a barcode scanner, a visual light camera, athermal camera, a light source, a lens, or an image sensor. A data filerepresentative of a captured image or content of a scanned image can bestored in the memory 47 within the captured data 64. As an example, thecaptured image can include one or more of the following: an image of thevehicle 1, an image of some portion of the vehicle 1, such as a portionof the vehicle 1 damaged in a collision, a license plate attached to thevehicle 1, or a VIN label attached to the vehicle 1. As another example,the captured image can include image data of a scanned barcode, such asthe barcode on a VIN label attached to the vehicle 1.

The audio device 46 can include one or more audio devices. In someimplementations, the audio device 46 can include one or more microphonesand/or one or more speakers. The connection mechanism 50 connected tothe audio device 46 can include electrical circuitry for providing theprocessor 40 with inputs representing voice commands received by the oneor more microphones. The voice commands can include commandsrepresenting selections and/or information that is described as beinginput by use of the keypad 44. The processor 40 can output signals tothe one or more speakers to cause one or more speaker to produce audiblesounds. As an example, the audible sounds can include instructions forusing the scanner 8.

5. Other Scanner Components

The connection mechanism 50 can include any of a variety of conductionsto carry data, communications, and/or signals between the componentsconnected to the connection mechanism 50. As an example, the connectionmechanism 50 can include a copper foil trace of a printed circuit board,a wire, or some other conductor.

The power supply 48 can be configured in any of a variety ofconfigurations or combinations of the variety of configurations. As anexample, the power supply 48 can include circuitry to receive AC currentfrom an AC electrical supply (e.g., electrical circuits connected to anelectrical wall outlet) and convert the AC current to a DC current forsupplying to one or more of the components within the scanner 8. Asanother example, the power supply 48 can include a battery or be batteryoperated. As yet another example, the power supply 48 can include asolar cell or be solar operated. The power supply 48 can includeelectrical circuits to distribute electrical current throughout thescanner 8. Other example configurations of the power supply 48 arepossible.

The housing 49 can surround at least a portion of the processor 40, atleast a portion of the network transceiver 41, at least a portion of theVCT 42, at least a portion of the display 43, at least a portion of thecapture device 45, at least a portion of the keypad 44, at least aportion of the memory 47, and/or at least a portion of the connectionmechanism 50. The housing 49 can be referred to as an enclosure. Thehousing 49 can support a substrate. At least a portion of the processor40, at least a portion of the network transceiver 41, at least a portionof the VCT 42, at least a portion of the display 43, at least a portionof the capture device 45, at least a portion of the keypad 44, at leasta portion of the memory 47 and/or at least a portion of the connectionmechanism 50 can be mounted on or connect to the substrate. The housing49 can be made from various materials. For example, the housing 49 canbe made from a plastic material (e.g., acrylonitrile butadiene styrene(ABS)) and a thermoplastic elastomer used to form a grip on the housing49.

6. Memory Content

The memory 47 stores computer-readable data. In an exampleimplementation, the memory 47 can be arranged like and/or include thesystem memory 654 and/or the storage device 660 shown in FIG. 19. Inthose or in different implementations, the memory 47 can store one ormore of the following: the CRPI 60, a vehicle model identifier 61, DTCdata 62, a vehicle portion identifier 63, captured data 64, an image 65,vehicle reference data (VRD) 66, a display screen 67, a collision report68, crash and damage data (CADD) 69, or a technical service bulletin(TSB) and position statement 70. FIG. 3B illustrates an exampleimplementation in which the memory 47 stores the CRPI 60, the vehiclemodel identifier 61, the DTC data 62, the vehicle portion identifier 63,the captured data 64, the image 65, the VRD 66, CADD 69, and the displayscreen 67.

The vehicle model identifier 61 includes data representing attributes ofa vehicle, such as a vehicle previously and/or presently operativelyconnected to the scanner 8. As an example, the attributes can includeattributes (e.g., a VIN) that the scanner 8 and/or the server 9 can useto distinguish a particular vehicle from all other vehicles. As anotherexample, the attributes can include attributes that the scanner 8 and/orthe server 9 can use to distinguish a class of vehicles including theparticular vehicle from all other classes of vehicles. For instance, theattributes of the vehicle model identifier 61 can include a portion ofthe VIN (e.g., make and model) of the vehicle 1, the M/M of the vehicle1, the Y/M/M of the vehicle 1, or the Y of the vehicle. The processor 40and/or the network transceiver 41 can transmit the vehicle modelidentifier of the vehicle 1 to the server 9 to request data regardingthe vehicle 1, such as images of the vehicle model associated with thevehicle 1 for storing in the image 65, or VRD associated with thevehicle model associated with the vehicle 1 for storage in the VRD 66.

The DTC data 62 includes DTC data regarding DTC(s) that can be set inthe vehicle 1. In some instance, the DTC data 62 can indicate no DTCis/are set in the vehicle 1. In other instances, the DTC data 62indicates one or more DTC are set in a component of the vehicle 1. As anexample, the DTC set in the vehicle 1 can include the DTC referred toas: (1) B0051: air bag deployment commanded, (2) B0520: rear dischargetemperature sensor malfunction, (3) B1182: TPMS right front malfunction,(4) C0040: right front wheel speed circuit malfunction, (5) C0070: rightfront ABS solenoid #1 circuit malfunction, and (6) C0085: left rear ABSsolenoid #2 circuit malfunction.

The DTC data 62 can include DTC data associated with a DTC set in thevehicle 1. As an example, the DTC data associated with the DTC caninclude data indicating a status (e.g., current, pending, or history) ofthe DTC. The processor 40 and/or the VCT 42 can transmit a VDM torequest the data associated with the DTC and receive, from the ECU thatset the DTC, a VDM including the data associated with the DTC. The dataassociated with a DTC can be referred to as extended DTC data.

As an example, the data associated with the DTC can include dataindicating a number of drive cycles, key cycles, or warm-up cycles sincethe DTC was set or since the MIL indicative of the DTC being set hasbeen in the power-on state. For instance, an ECU configured to set a DTCindicative of a tire pressure monitor sensor (TPMS) malfunction canstore data that indicates the number of key cycles since the DTCindicative of a TPMS malfunction was set current or caused the TPMS MThto illuminate.

As another example, the data associated with the DTC can include freezeframe data. The ECU can store the freeze frame data when the ECU sets aDTC to a status of current. The ECU can store the freeze frame data fora number of drive, key, or warm-up cycles before erasing the freezeframe data. The VDM including freeze frame data can indicate the numberof drive, key, or warm-up cycles that have occurred since the DTC wasset. The freeze frame data can be stored and retrieved from asupplemental restraint system (SRS) ECU and/or by another ECU in thevehicle, such as a powertrain system ECU.

As still yet another example, the data associated with the DTC caninclude a time stamp indicative of when the DTC was set current in thevehicle. The time stamp can include date information in addition to timeinformation.

The vehicle portion identifier 63 includes an identifier indicative of aportion of a vehicle, such as portion of the vehicle 1. In accordancewith an example implementation, the portion of the vehicle can includean exterior portion of the vehicle. For a vehicle, such as anautomobile, an exterior portion of the vehicle can include a body panel,such as a hood, an exterior door panel, a windshield, a quarter panel,among others. In the preceding and/or in another example implementation,the portion of a vehicle can include an interior portion of a vehicle,such as a front passenger compartment, a rear passenger compartment, anunder-hood portion, among others. As an example, the vehicle portionidentifier 63 can indicate a vehicle portion shown in Table 2 or Table 3(shown below) or a body panel name. A portion of the vehicle can includea portion of the vehicle damaged during a collision. As another example,the portion of the vehicle can include a portion of the vehicle at whicha malfunctioning component is located. Other examples of the vehicleportion identifier 63 are available. The processor 40 can determine aportion of the vehicle 1 that is to be stored as at least part of thevehicle portion identifier 63.

The captured data 64 can include data generated by the capture device45. The captured data 64 can include one or more image files generatedby the capture device 45. As an example, the captured data 64 caninclude an image file representing an image showing some portion of thevehicle 1. The processor 40 can use the image showing some portion ofthe vehicle 1 for various purposes, such as identifying the vehiclemodel associated with the vehicle 1. The selector 118 shown in FIG. 6Bpertains to identifying the vehicle model associated with the vehicle 1using an image captured by the capture device 45. As another example,the processor 40 can use the image showing some portion of the vehicle 1to determine a damaged portion of the vehicle 1 at which the vehicle wasdamaged during a collision.

The image 65 can include one or more images files. The processor 40and/or the network transceiver 41 can request and receive from theserver 9 an image file for storing in the image 65. The image 65 caninclude image files associated with a single vehicle model or eachvehicle model of multiple different vehicle models. As an example, thelatter type of image file can include an image file representing allpick-up trucks, an image file representing all two-door automobiles, oran image file representing all four-door automobiles.

An image file in the image 65 can be used for various purposes. Forinstance, an image file in the image 65 can be displayed by the display43 along with a vehicle grid, such as a vehicle grid 134 shown in FIG.9B. The processor 40 can determine a vehicle grid location displayed onthe display 43 has been selected and responsively determine that aportion of a vehicle displayed within the selected vehicle grid locationhas been selected. Selection of the portion of the vehicle can, but neednot necessarily, indicate that the selected portion of the vehicle isdamaged. In some implementations, the image file can include the vehiclegrid 134, whereas in other implementations, the vehicle grid is separatefrom the image file. Allowing a user to select a portion of a vehiclecan reduce the burden on a processor from having to determine theportion of the vehicle by comparing two or more images of the vehicle.Additionally, in some implementations, the processor 40 can select avehicle grid location based on a DTC associated with the DTC and/or avehicle component associated with the DTC being located in a portion ofthe vehicle represented by the vehicle grid location.

A vehicle grid (e.g., the vehicle grid 134, 148, 881 shown in thedrawings) displayed on the display 43 can be displayed with grid lines,such as grid lines that identify a perimeter of a vehicle grid location.The vehicle grid locations shown in the drawings are shown as beingrectangular. A vehicle grid location can be a shape other thanrectangular. For instance, a vehicle grid location can be a shape thatis at least partially defined by a contour of a portion of a vehicle.

As another example, an image file in the image 65 can be used by theprocessor 40 for comparison to an image file generated by the capturedevice 45. Based on the comparison, the processor 40 can make variousdeterminations, such as a determination that a portion of a vehiclerepresented in both of those image files corresponds to a damagedportion of that vehicle. Configuring the processor 40 to determine adamaged portion of a vehicle can increase accuracy of determining alldamaged portions of the vehicle in situations when a user overlooks oneor more damaged portions of the vehicle.

The VRD 66 includes vehicle reference data regarding a vehicle, such asthe vehicle 1. FIG. 16A shows example VRD 300. The VRD 300 includes VRD301 that is associated with a first vehicle model (e.g., a vehicle modelreferred to as VM1), VRD 340 that is associated with a second vehiclemodel (e.g., a vehicle model referred to as VM2), and VRD 350 that isassociated with a third vehicle model (e.g., a vehicle model referred toas VM3). The VRD 340 and the VRD 350 can include types of VRD similar tothe types of VRD in the VRD 301 except that the VRD 340, 350 isassociated with a different vehicle model. The VRD 66 can include VRDfor one or more vehicle models. The scanner 8 can request and receiveVRD from the server 9 to store as the VRD 66. That request can betransmitted by the scanner 8 upon determining a vehicle model of thevehicle connected to the scanner 8. As an example, VM1 can represent avehicle model described or shown elsewhere in the application as a “2017Beta Tango,” VM2 can represent a vehicle model, such as a “2018 RushBarchetta,” and VM3 can represent a vehicle model, such as a “2018 Jeep®Rubicon®.” The VRD 66 can, but need not necessarily, include an XML filecontaining VRD regarding one or more vehicle models.

The VRD 301 can include data indicating one or more of: a type of ECU302, an ECU ID 303 used within a VDM, a VDM protocol 304, a DTC 305, arelated component 306, a rate 307, a component location 308, and/or aprocedure 309. Each of those items shown in a single row in FIG. 16A canbe associated with that DTC and related component. The rate 307 canindicate whether a DTC is commonly set or rarely set. The rate 307 caninclude data the server 9 determines from repair order data regardinginstances of vehicles of the vehicle model VM1 being serviced.

The VRD 301 can include other reference data associated with the vehiclemodel, such as warnings 310, procedures 311, VDM 312, and vehicle imagedata 313. The warnings 310 can be associated with a damaged portion ofthe vehicle, such as a “warning #2” 330 associated with a LRQ, RRQ, LR,and RR of the vehicle 1. The procedures 311 can include procedures suchas a circuit repair procedure, a remove and replace (R&R) procedure, areset procedure, an initialization procedure, a program procedure, and acalibration procedure, or any other procedure applicable to servicingthe vehicle 1. The VDM 312 can include a VDM recognizable to the vehicle1, such as VDM to request a VIN from the PCM ECU. The vehicle image data313 can include identifiers of images that show reference portions ofthe vehicle 1. The vehicle image data 313 can include identifiers ofmultiple images that show the same reference portion of the vehiclemodel, but with different vehicle colors, such as an image of the rightside of vehicle IMG901G showing the right side painted green and animage of the right side of the vehicle IMG901B showing the right sidepainted blue. The image identifier can be used to generate a displaypresentation including a selector to a vehicle image. The processor 40can request an image associated with an image identifier in response todetermine the selector to the vehicle image was selected.

The VRD 301 can include PID parameter data 361 that is associated with aDTC, such as the DTC P0095 or some other DTC. The PID parameter data 361can include parameter values for each PID that is associated with theDTC. For instance, FIG. 16A shows that PID1, PID2, PID3, PID4, and PID5are associated with the DTC P0095. The PID parameter data 361 caninclude parameters for PID1 to PID5 captured from a vehicle associatedwith the vehicle model VM1 operating without any DTC set at a particularmileage or within a particular mileage range M1 (e.g., 50,000 miles or50,000 to 60,000 miles). The PID parameter data 361 can include faultparameter values indicative of when the DTC P0095 sets to active. Aprocessor can compare the PID parameter data 361 to PID parameterscaptured from the vehicle 1 for use in making a determination of whethera setting of a DTC is collision-related. The top row of parameter valuescan be mean operating parameter values when the vehicle is operatingwithout any DTC set. The bottom row of parameter values are the faultparameter values.

The VRD 301 can include VRD including POI damage data and PRCD data,such as the VRD 800 shown in FIG. 16B. The VRD 800 includes VRD thatpertains to multiple vehicle models, such as all vehicle models, and VDRthat pertains to a single vehicle model. VRD 801 is an example of VRDthat pertains to multiple vehicle models. The VRD 801 includes POIdamage data 804 and PRCD data 805, 806 that pertain to theaforementioned multiple vehicle models.

VRD 802 is an example of VRD that pertain to a single vehicle model. Forinstance, the VRD 802 pertains to vehicles identified by the vehiclemodel VM1. The VRD 802 includes POI damage data 807, and PRCD data 808,809 that pertains to the POI damage data 807. The VRD 802 includes POIdamage data 810, and PRCD data 811, 812 that pertain to the POI damagedata 810. The VRD 802 includes VRD data 819 that includes identifiersfor restraint and/or safety components for vehicle model VM1. The VRDdata 819 can include PRCD data 820, 821, 822, 823, 824 indicative ofcomponents that can, but need not necessarily, be located in a POIportion of the damaged vehicle. As an example, the PRCD data 820, 821,822, 823, 824 indicates a collapsible steering column identifier, aninstrument panel knee bolsters identifier, a seat belts identifier, aseatbelt retractor pre-tensioners identifier, and an airbags identifier,respectively.

VRD 803 is another example of VRD that pertain to a single vehiclemodel. For instance, the VRD 803 pertains to vehicles identified by thevehicle model VM2. The VRD 803 includes POI damage data 813, and PRCDdata 814, 815 that pertains to the POI damage data 813. The VRD 803includes POI damage data 816, and PRCD data 817, 818 that pertains tothe POI damage data 816. After determining POI damage to a vehicle, theprocessor 40, 440 can determine, from the VRD 800, PRCD that pertains tothat vehicle and cause the display 43 to display the PRCD. In an exampleimplementation, displaying the PRCD can include displaying one or morefrom among: textual PRCD, graphical PRCD, and/or an image of PRCD.

The VRD 301 can include multi-stage air bag data 867. The processor 40can refer to the multi-stage air bag data 867 to determine air bag(s) inthe vehicle that have multiple initiators, such as a front driver sideair bag and a front passenger side air bag. The multi-stage air bag data867 can include data indicating which DTC of the SIR ECU pertain tosquibs being live or used, and/or data indicating parameters to refer todetermine when a DTC pertaining to squibs being live or used were setactive.

Returning to FIG. 3B, the display screen 67 can include one or moredisplay screens. Each display screen can include one or more files forgenerating a display screen that can be displayed on the display 43. Inaccordance with an example implementation, a display screen displayed onthe display 43 can include a menu and/or a graphical user interface(GUI). In accordance with those other implementations, a display screendisplayed on the display 43 can include other content stored in thememory 47, such as image of the image 65. A display screen displayed onthe display can include one or more virtual controls. The processor 40can determine a display screen to display on the display in response toselection of a virtual control displayed on the display 43. Exampledisplay screens are shown in and described with respect to FIG. 6A toFIG. 15N. In one respect, a display screen can be static in that theprocessor 40 does not change or supplement the display screen. Inanother respect, a display screen can be dynamic in that the processor40 changes or supplements the display screen before, while, or afterbeing displayed. The network transceiver 41 can receive a display screenfrom the server 9. The display screen received from the server 9 can bestored in memory 47 as at least part of the display screen 67.

Next, FIG. 3C illustrates an example implementation in which the memory47 stores the CRPI 60, the vehicle model identifier 61, the DTC data 62,the vehicle portion identifier 63, the captured data 64, the image 65,the VRD 66, the display screen 67, a collision report 68, the CADD 69,and the TSB and position statement 70.

The CADD 69 includes crash data generated by a vehicle involved in acollision and damage data regarding that vehicle. The processor 40and/or the VCT 42 can receive the crash data from an SRS ECU in thevehicle or one or more separate ECU in the vehicle that store crashdata. The processor 40 and/or the VCT 42 can request the crash data bysending a VDM to the SRS ECU and/or the one or more separate ECU storingthe crash data. The crash data can be referred to as “event data” and aECU that stores the event data can be referred to as an “event datarecorder.” The processor 40 can generate at least a portion of thedamage data based on inputs entered using the display 43, the keypad 44,the capture device 45, and/or the audio device 46. The CADD 69 caninclude CADD for multiple vehicles, such as multiple vehicles that wereconnected to the VCT 42.

FIG. 3D is a diagram showing an example of the CADD 69 in accordancewith the example implementations. As shown in FIG. 3D, the CADD 69include crash data 75 and damage data 77. The crash data 75 includesdata indicating a vehicle model of the vehicle involved in the collisionand time and date data indicative of when the collision to theidentified vehicle occurred. The vehicle model of the crash data 75 isthe 2017 Beta Tango (referred to as VM1 herein).

The crash data from a vehicle can include pre-crash data (e.g., datagenerated by a vehicle prior to the collision), intra-crash data (e.g.,data generated by a vehicle during the collision), and post-crash data(e.g., data generated by a vehicle after the collision). FIG. 3D showstime values −5, −4, −3, −2, and −1 associated with crash data parameters(vehicle speed (VS), engine revolutions per minute (RPM), brakesapplied, and seat belt fastened). The time values −5, −4, −3, −2, and −1can, respectively, represent times five, four, three, two, and onesecond(s) before the collision was detected. The vehicle speed and timevalues can determine a delta velocity (ΔV) parameter. Other examples ofcrash data parameters include traction control system (TCS) (on or off),anti-lock brake system (ABS) (on or off), principal degree of force(PDOF), lateral acceleration, and YAW. The types of crash dataparameters generated by a particular vehicle model are typically thesame, although the values of those crash data parameters generated byvehicles of the particular vehicle model can vary from each other basedon circumstances of the collision.

The damage data 77 includes data indicating vehicle componentsidentified as being damaged during a collision to the vehicle. As shownin FIG. 3D, the vehicle components include the right front fender, theB-pillar, the front row right seat belt retractor pre-tensioner, and theright front wheel speed sensor. As an example, the wheel speed sensorcould be added to the damage data 77 based on a DTC set in the vehicleand data pertaining to that DTC, such as the data pertaining to the DTCC0040 shown in FIG. 10B. As another example, the right front fendercould be added to the damage data 77 based on a determination theprocessor 40 makes based on an image of damaged vehicle or a selectionmade via the display 43.

The network transceiver 41 can transmit the CADD 69 to the server 9 forstorage within CADD 467 (shown in FIG. 4A). The network transceiver 41can receive damage data from the server 9 for including within the CADD69. The damage data provided by the server 9 could include damage databased on multiple vehicles involved in collisions, such as multiplevehicles associated with a common vehicle model, such as the vehiclemodel for VM1. The damage data provided by the server 9 could bepossible related collision damage (PRCD) that the processor 40 couldoutput on the display 43 to prompt a user to inspect the vehicle to seeif the PRCD is applicable to the vehicle being worked on.

The collision report 68 includes a report the processor 40 generatesbased, at least in part, on data the processor 40 determines fromvarious sources, such as one or more of the following: the vehicle 1,the server 9, the NCS 24, 25, 26, or data received by the scanner 8.FIG. 17 shows example data that can be part of the collision report 68.The processor 40 can output the collision report 68 to the display 43for displaying on the display 43. The processor 40 and/or the networktransceiver 41 can transmit the collision report 68 to one or more ofthe following: the server 9 or the NCS 24, 25, 26.

The TSB and position statement 70 can include a TSB and/or positionstatement related to a vehicle model determined by the processor 40 andrelated to POI damage and/or PRCD pertaining to the determined vehiclemodel. A TSB and/or position statement can be related to a DTC, such asa DTC determined to be collision-related. A TSB and/or positionstatement stored in the TSB and position statement 70 can include a TSBand/or position statement produced and/or received from a vehicle OEM ora vehicle component OEM. The TSB and/or position statement from an OEMcan be augmented with a tag(s) for the processor 40 to determine thatthe TSB and/or position statement is related to the determined vehiclemodel and the POI damage and/or the PRCD. A TSB and/or positionstatement can include information from the vehicle or vehicle componentOEM regarding a vehicle recall or repair campaign.

In general, the CRPI 60 can include program instructions to performfunctions described in this description as being performed by thescanner 8 or a component of the scanner 8. For example, the CRPI 60 caninclude program instructions to perform one or more or all of thefunctions of the set of functions 500 shown in FIG. 5A and/or one ormore or all of the functions of the set of functions 725 shown in FIG.18A. Some examples of some particular program instructions of the CRPI60 (executable by the processor 40) are described in the followingsection.

7. Example CRPI

The CRPI 60 can include program instructions to cause the processor 40to transmit or cause the VCT 42 to transmit a VDM to the vehicle 1. ThatVDM can include any VDM described as being transmitted to a vehicle. TheCRPI 60 can include program instructions to cause the processor 40 toattempt to transmit or cause the VCT 42 to attempt to transmit a VDM tothe vehicle 1. Attempting to transmit a VDM can occur while the scanner8 is trying to automatically identify a vehicle model of the vehicle 1.The CRPI 60 can include program instructions to cause the processor 40to receive a VDM transmitted by the vehicle 1 to the scanner 8.

The CRPI 60 can include program instructions to cause the processor 40to transmit or cause the network transceiver 41 to transmit acommunication onto the network 11. The CRPI 60 can include programinstructions to cause the processor 40 to receive a communicationtransmitted over the network 11 to the scanner 8.

The CRPI 60 can include program instructions to cause the scanner 8 tochange its operating states, such as performing functions to change froma power-on state to a power-off state or to change from the power-offstate to the power-on state. The CRPI 60 can include programinstructions to determine a key of the keypad 44 has been pressed orotherwise manipulated to indicate a user action, and to determine anaction to perform in response to determining the key has been pressed orotherwise manipulated. The CRPI 60 can include program instructions todetermine a virtual control displayed on the display 43 has been pressedto indicate a selection has been entered, and to determine an action toperform in response to determining the virtual control was selected. TheCRPI 60 can include program instructions to cause the display 43 tooutput a display screen stored in the display screen 67, such as anydisplay screen shown in FIG. 6A to FIG. 15N.

The CRPI 60 can include program instructions to store an image capturedby the capture device 45 within the captured data 64. The CRPI 60 caninclude program instructions to determine an image stored in the image65 and to display on the display 43 the image stored in the image 65.The CRPI 60 can include program instructions to display the image withinor as part of the vehicle grid 134. The CRPI 60 can include programinstructions to determine a portion of the vehicle grid 134 has beenselected and the portion of vehicle shown in the determined portion ofthe vehicle grid was damaged in a collision. The CRPI 60 can includeprogram instructions to perform optical character recognition (OCR) toidentify characters in a captured image. The CRPI 60 can include programinstructions to decode a bar code scanned by the capture device 45.

The CRPI 60 can include program instructions to receive PRCD data thenetwork transceiver 41 receives from the server 9. The CRPI 60 caninclude program instructions to store the PRCD data in the memory 47(e.g., within the CADD 69) and/or to cause the display 43 to display thePRCD data. The CRPI 60 can include program instructions to cause theprocessor 40 to determine (e.g., confirm) whether or not the PRCDdisplayed on the display is RCD. As an example, the processor 40 canmake that determination by receiving an input to the display 43 or viathe keypad 44 indicating the PRCD is RCD. The CRPI 60 can cause thenetwork transceiver 41 to transmit to the server 9 a communicationindicating whether or not the PRCD indicated by the PRCD data wasdetermined to be RCD. The CRPI 60 can include program instructions tocause the processor 40 to add to the collision report 68 identifiers ofthe PRCD determined to be RCD.

The CRPI 60 can include program instructions to determine whether an airbag squib on a vehicle connected to the scanner 8 is “live” or “used.”For brevity, those CRPI are referred to hereafter in this description as“squib CRPI.” A used squib is a squib that has initiated deployment ofan air bag. A live squib is a squib that has not initiated deployment ofan air bag. Special handling instructions exist for some live squibs.The squib CRPI can be configured to be executed in response to theprocessor 40 determining the squib status selector 114 was selected.Additionally or alternatively, the squib CRPI can be configured to beexecuted automatically in response to a trigger event. As an example,the trigger event can connection of the scanner 8 to a vehicle, thescanner 8 transmitting a VDM to an SIR ECU, and/or the scanner 8receiving a VDM from an SIR ECU. The squib CRPI can be configured tocause the processor 40 and/or the VCT 42 to transmit to the SIR ECU aVDM including a request for DTC and to receive from the SIR ECU a VDMindicative of DTC set in the SIR ECU DTC. The squib CRPI can beconfigured to cause the processor 40 and/or the VCT 42 to transmit tothe SIR ECU a VDM including a request for data indicating a time wheneach DTC set active was set active and to receive from the SIR ECU a VDMindicating a time when each DTC set active was set active.

The squib CRPI can cause the processor 40 to determine which DTC setactive by the SIR ECU is/are indicative of an air bag squib status. Asan example, the processor 40 can refer to the multi-stage air bag data867 to make that determination. For instance, the processor 40 can referto the multi-stage air bag data 867 to determine the front driver andfront passenger air bags are multi-stage air bags, each with two squibsand the SIR ECU can set a respective DTC indicative of each of thosesquibs being open-circuited.

The squib CRPI can be configured to cause the processor 40 to determinea status (e.g., active or inactive) of a DTC that indicates a squib fora particular air bag (e.g., air bag N) is open circuited. Moreover, ifthe processor 40 determines the DTCs indicating each squib for adual-squib air bag is open-circuited are active, the processor 40 canresponsively determine an amount of time existing between each of thoseDTC for the dual-squib air bag going active. The processor 40 cancompare the determined amount of time to a squib activation threshold todetermine whether or not the amount of time exceeds the squib activationthreshold. As an example, the squib activation threshold can be oneminute, five minutes, ten minutes, or fifteen minutes.

Table 1 shows example squib statuses the processor 40 can determine byexecuting the squib CRPI. In Table 1, “Null” represents that a timecomparison is not needed to determine the squib status.

TABLE 1 DTC status—Squib #1 DTC status—Squib #2 Squib open for air bag Nopen for air bag N Time Comparison Status Active Active Time differencefor squib Squib #1—used #1 and squib #2 less than Squib #2—usedthreshold Active Active Time for squib #2 exceeds Squib #1—used by timefor squib #1 by at Squib #2—live least threshold Active Active Time forsquib #1 exceeds Squib #1—live by time for squib #2 by at Squib #2—usedleast threshold Active Inactive Null Squib #1—used Squib #2—liveInactive Active Null Squib #1—live Squib #2—usedAs an example, an SIR ECU in the vehicle 1 can be configured to set aDTC B1115 when squib #1 of a front driver side air bag isopen-circuited, a DTC B1116 when squib #2 of the front driver side airbag is open-circuited, a DTC B1117 when squib #1 of a front passengerside air bag is open-circuited, a DTC B1118 when squib #2 of the frontpassenger side air bag is open-circuited. The processor 40 executing thesquib CRPI can receive a VDM from an SIR ECU in that vehicle indicatingthat DTC B1115, B1116, and B1117 are active. That VDM may not includedata indicating DTC B1118 is active. The processor 40 can use thatomission to determine that DTC B1118 is inactive. The processor 40 canreceive data indicating the DTC B1115 was set active at 7:00:05 AM onApr. 6, 2018 and the DTC B1116 was also set active at 7:00:05 on thesame date. The processor 40 can determine that a difference in those twoDTC activation times is less than the squib activation threshold (e.g.,ten minutes). Referring to Table 1, the processor 40 can determine thatsquib #1 and squib #2 of the front passenger side air bag are used, andsquib #1 of the front passenger side air bag is used and the squib #2for the front passenger side air bag is live. The processor 40 canoutput the display screen 854 and/or the squib status information 863 tothe display 43 in response to determining the squib status of those twofront air bags.

B. Example Server

Next, FIG. 4A is a simple block diagram of the server 9, in accordancewith an example implementation. As shown in FIG. 4A, the server 9includes a processor 440, a network transceiver 441, and a memory 446.Two or more of those components can be operatively connected via asystem bus, network, or other connection mechanism 447. The server 9also includes a power supply 448 and a housing 449.

1. Processor

The processor 440 can include one or more processors. The exampleprocessors described above with respect to processor 40 are applicableto the processor 440. The processor 440 can be configured to executeCRPI, such as the CRPI 460 stored in the memory 446. The processor 440can be configured to execute hard-coded functionality in addition to oras an alternative to software-coded functionality (e.g., via CRPI). Theprocessor 440 can be configured (e.g., programmed) to perform anyfunction or combination of functions described herein as being performedby the server 9. The processor 440 can be configured (e.g., programmed)to perform any of the determining functions described as being performedby the processor 40.

2. Memory

The memory 446 includes a single memory or multiple memories. Two ormore of the multiple memories can be the same type of memory ordifferent types of memories. The memory 446 is configured to storecomputer-readable data, such as the example memory content discussedbelow. The example types of memories described above with respect to thememory 47 are applicable to the memory 446.

3. Transceiver

The network transceiver 441 can transmit any data or communicationdiscussed as being transmitted, output, or provided by the server 9 toone or more of the following: the scanner 8, the NCS 24, 25, 26, or theinsurance company 18, 19, 20. The network transceiver 441 can receiveany data or communications discussed as being received by the server 9or the network transceiver 441 from one or more of the following: thescanner 8, the NCS 24, 25, 26, or the insurance company 18, 19, 20. Thenetwork transceiver 441 can transmit a collision report 469 to one ormore of the following: the scanner 8, the NCS 24, 25, 26, or theinsurance company 18, 19, 20.

Some vehicles are equipped with a telematics system for communicatingwith an NCS operated by a telematics service provider. A typicaltelematics system includes a cellular network transceiver configured fortransmitting a VDM to the telematics service provider to request aservice, such as call a first responder to provide emergency services atthe vehicle involved in a collision. The cellular network transceiver isalso configured for receiving a VDM from the telematics serviceprovider, such a VDM to cause the vehicle doors to unlock. The VDMtransmitted by the cellular network transceiver can be arrangedaccording a VDM protocol different than the VDM protocol of messagestransmitted to the DLC 2. The telematics service provider can include anetwork transceiver to receive the VDM transmitted by the cellularnetwork transceiver in the vehicle and to transmit a VDM to be receivedby the cellular network transceiver in the vehicle. The networktransceiver 441 can be configured to receive a VDM transmitted by thecellular network transceiver in the vehicle and to transmit a VDM to bereceived by the cellular network transceiver in the vehicle. The contentof a VDM transmitted to the vehicle by the network transceiver 441 canbe identical to the content of a VDM transmitted to the vehicle by theVCT 42. The content of a VDM transmitted by the vehicle to the networktransceiver 441 can be identical to the content of a VDM transmitted bythe vehicle to the VCT 42.

The server 9 can also include a communication interface 667, a networkcontroller 668, and a communication port 669, as shown in FIG. 19.

4. Other Server Components

The connection mechanism 447 can include any of a variety of conductionsto carry communications or data between the components connected to theconnection mechanism 447. As an example, the connection mechanism 447can include a copper foil trace of a printed circuit board, a wire, orsome other conductor.

The power supply 448 can be configured in any of a variety ofconfigurations or combinations of the variety of configurations. As anexample, the power supply 448 can include circuitry to receive ACcurrent from an AC electrical supply (e.g., electrical circuitsconnected to an electrical wall outlet) and convert the AC current to aDC current for supplying to one or more of the components within theserver 9. As another example, the power supply 448 can include a batteryor be battery operated. As yet another example, the power supply 448 caninclude a solar cell or be solar operated. The power supply 448 caninclude electrical circuits to distribute electrical current throughoutthe server 9. Other examples of the power supply 448 are available.

The housing 449 can surround at least a portion of the processor 440, atleast a portion of the network transceiver 441, at least a portion ofthe memory 446, or at least a portion of the connection mechanism 447.The housing 449 can be referred to as an enclosure. The housing 449 cansupport a substrate. At least a portion of the processor 440, at least aportion of the network transceiver 441, at least a portion of the memory446, or at least a portion of the connection mechanism 447 can bemounted on or connected to the substrate. The housing 449 can be madefrom various materials. The housing 449 can include a computer rack.

5. Memory Content

The memory 446 stores computer-readable data. As an example, the memory446 stores one or more of the following: the CRPI 460, a vehicle modelidentifier 461, a DTC data 462, a vehicle portion identifier 463, animage 464, an image library 465, VRD 466, CADD 467, a display screen468, a collision report 469, and/or a TSB and position statement 470.

The vehicle model identifier 461 includes data the server 9 storesregarding the vehicle 1. The vehicle model identifier 461 can beconfigured like the vehicle model identifier 61. The processor 440and/or the network transceiver 441 can receive the vehicle modelidentifier 61 from the scanner 8 and store the received vehicle modelidentifier as the vehicle model identifier 461. Based on the vehiclemodel identifier 461, the processor 440 can provide the scanner 8 withdata regarding the vehicle 1, such as images of the vehicle modelassociated with the vehicle 1 for storing in the image 65, vehiclereference data associated with the vehicle model associate with thevehicle 1 for storage in the VRD 66.

The DTC data 462 includes DTC data indicative of the DTC(s) set in thevehicle 1. The processor 440 and/or the network transceiver 441 canreceive the DTC data 62 from the scanner 8 or the vehicle 1 and storethe received DTC data as the DTC data 462. Therefore, the DTC data 462can include any of the DTC data described as being a part of the DTCdata 62.

The vehicle portion identifier 463 includes an identifier indicative ofa portion of the vehicle 1 damaged during a collision. The processor 440and/or the network transceiver 441 can receive the vehicle portionidentifier 63 from the scanner 8 or the vehicle 1 and store the receivedvehicle portion identifier as the vehicle portion identifier 463. Thevehicle portion identifier 463 can indicate a damaged portion shown inTable 2 or in Table 3 or a body panel name. Other examples of thevehicle portion identifier 463 are available.

The image 464 includes an image captured by a capture device, such asthe capture device 45. The processor 440 and/or the network transceiver441 can receive an image from the scanner 8 or the vehicle 1 and storethe received image as the image 464. The image 464 can include multipleimages captured by the capture device 45. As an example, the image 464can include an image showing some portion of the vehicle 1. Theprocessor 440 can use the image showing some portion of the vehicle 1for various purposes, such as identifying the vehicle model associatedwith the vehicle 1. As another example, the processor 440 can use theimage showing some portion of the vehicle 1 to determine a damagedportion of the vehicle 1 at which the vehicle was damaged during acollision.

The image library 465 can include one or more images associated with avehicle model associated with the vehicle 1. The processor 440 and/orthe network transceiver 41 can provide the scanner 8 with an image forstoring in the memory 47 as the image 65. An image in the image library465 can be used for various purposes. For instance, an image in theimage library 465 can be provided to the scanner 8 for displaying withina vehicle grid, such as the vehicle grid 134. As another example, animage in the image library 465 can be used by the processor 440 tocompare to an image provided by the scanner 8. The image library 465 caninclude images associated with each vehicle model of multiple differentvehicle models.

The VRD 466 includes vehicle reference data regarding the one or morevehicles. As an example, the VRD 466 can include or be configured withVRD like the VRD 300 shown in FIG. 16A. The processor 440 can refer tothe VRD 466 to determine VRD to include in a display screen beinggenerated for the scanner 8.

The CADD 467 includes crash data and damage data. The crash data caninclude crash data one or more scanners obtained from vehicles involvedin collisions. For example, the processor 440 and/or the networktransceiver 441 can receive the crash data from the scanner 8. Theprocessor 440 and/or the network transceiver 441 can receive the damagedata from scanner 8 and/or an NCS, such as the NCS.

FIG. 4B is a diagram showing an example of the CADD 467. The CADD 467includes crash data and damage data regarding multiple collisions andmetadata associated with the crash and damage data. As shown in thefigure, the CADD 467 includes CADD 475 for a collision event #1, CADD476 for a collision event #2, CADD 477 for a collision event #3, andCADD 478 for a collision event #N. As an example, #N can represent acurrent greatest number of collision events for which the CADD 467includes CADD (for all vehicle models or a particular vehicle model).For example, #N could be 5,000, 20,000, 1,000,000 or some other numbergreater than the 1 that pertains to a first collision (e.g., collisionevent #1). A skilled person will understand that the CADD 467 couldinclude crash and damage data for one collision event prior to crash anddamage data f or another collision event being added to the CADD 467.

The CADD 475 includes metadata 479 referencing a particular collisionevent, crash data 480, and damage data 481. Similarly, the CADD 476includes metadata 482 referencing a particular collision event, crashdata 483, and damage data 484, the CADD 477 includes metadata 485referencing a particular collision event, crash data 486, and damagedata 487, and the CADD 478 includes metadata 488 referencing aparticular collision event, and the crash data 75 and damage data 77.Similar to the crash data 75, the crash data 480, 483, 486 can includepre-crash data, intra-crash data, and/or post-crash data, a vehiclemodel identifier, and/or time and date data indicative of when theidentified vehicle was involved in a collision. The CADD 475, 476, 477,478 include vehicle model identifiers of a single vehicle model (i.e.,2017 Beta Tango, also referred to as VM1 herein). The CADD 467 caninclude CADD for more than one vehicle model.

Returning to FIG. 4A, the display screen 468 can include a displayscreen configured to be provided to the scanner 8 and shown on thedisplay 43. Example display screens are shown in and described withrespect to FIG. 6A to FIG. 15N. The scanner 8 can, for example, displaya display screen from the display screen 468 within a browser windowdisplayed on the display 43.

The collision report 469 includes a collision report regarding a vehicleconnected to the scanner 8. In one respect, the processor 440 generatesbased, at least in part, on data the processor 440 determines fromvarious sources, such as one or more of the following: the vehicle 1,the scanner 8, the NCS 24, 25, 26, or data received by the server 9. Inanother respect, the processor 440 and/or the network transceiver 441receives the collision report 68 from the scanner 8 and stores thereceived collision report as the collision report 469. FIG. 17 showsexample data that can be part of the collision report 469. The processor440 and/or the network transceiver 441 can transmit the collision report469 to one or more of the following: the scanner 8 or the NCS 24, 25,26.

The TSB and position statement 470 can include a TSB related to avehicle model determined by the processor 440 and related to POI damageand/or PRCD pertaining to the determined vehicle model. A TSB stored inthe TSB and position statement 470 can include a TSB produced and/orreceived from an OEM vehicle manufacturer. The TSB from the OEM vehiclemanufacturer can be tagged with tags for the processor 440 to determinethat the TSB is related to the determined vehicle model and the POIdamage and/or the PRCD.

In general, the CRPI 460 can include program instructions to performfunctions described in this description as being performed by the server9 or a component of the server 9. For example, the CRPI 460 can includeprogram instructions to perform one or more or all of the functions ofthe set of functions 500 shown in FIG. 5A and/or one or more or all ofthe functions of the set of functions 725 shown in FIG. 18A. Someexamples of some particular program instructions of the CRPI 460(executable by the processor 440) are described in the followingsection.

6. Example CRPI

The CRPI 460 can include program instructions to cause the processor 440to transmit or cause the network transceiver 441 to transmit a VDM tothe vehicle 1, or to transmit to the scanner 8 a request for the scanner8 to transmit a VDM to the vehicle 1. Those VDM can include any VDMdescribed as being transmitted to a vehicle. The CRPI 460 can includeprogram instructions to cause the processor 440 to receive a VDMtransmitted by the vehicle 1 to the server 9.

The CRPI 460 can include program instructions to cause the processor 440to transmit or cause the network transceiver 441 to transmit acommunication onto the network 11. The CRPI 460 can include programinstructions to cause the processor 440 to receive a communicationtransmitted over the network 11 to the server 9. The CRPI 460 caninclude program instructions to store an image received from the scanner8 as the image 464. The CRPI 460 can include program instructions todetermine an image stored in the image library 465 and to transmit thedetermined image to the scanner 8 for displaying on the display 43. TheCRPI 60 can include program instructions to determine a portion of adisplayed vehicle grid 134 has been selected and the portion of vehicleshown in the determined portion of the vehicle grid was damaged in acollision. The CRPI 460 can include program instructions to performoptical character recognition (OCR) to identify characters in a capturedimage. The CRPI 460 can include program instructions to decode a barcode scanned received from the scanner 8.

The CRPI 460 can include program instructions to determine possiblerelated collision data for a vehicle, such as a vehicle connected to thescanner 8. The server 9 can transmit the PRCD to the server 9. Theserver 9 can determine RCD for the vehicle by receiving, from thescanner 8, a communication indicating which PRCD was confirmed by thescanner 8. The server 9 can augment a collision report 469 withidentifiers of the RCD confirmed by the scanner 8.

The program instructions to determine PRCD can include programinstructions following a set of rules for determining PRCD. As anexample, those rules can include determining one or more crash dataparameters for the damaged vehicle that match and/or are within a rangeof similar crash data parameters obtained from one or more othervehicles. The one or more other vehicles can be the same vehicle modelas the vehicle connected to the scanner. The program instructions cancompare damage data associated with the crash data obtained from the oneor more other vehicles to the damage data associated with the vehicleconnected to the scanner 8, and determine damage data that is notincluded within the data damage associated with the vehicle connected tothe scanner 8.

As an example, the processor 440 can receive the crash data 75 and thecrash data 480 both pertain to vehicles associate with the vehicle modelVM1 and that one or more crash data parameters of the crash data 75match and/or are within a threshold of the same type of crash dataparameters in the crash data 480. For instance, those parameters caninclude the pre-crash vehicle speed values being within five MPH of eachother and the PDOF being within eight degrees (8°) of each other. Inthat case, the processor 440 can determine that the collision event #1associated with the CADD 475 and the damage data 481 is to be comparedto the damage data 77 in order to determine PRCD. Based on thatcomparison, the processor 440 can determine the PRCD includes: the rightfront brake set (e.g., brake shoes, brake rotor, and brake caliper), avehicle battery and a coolant reservoir, as those component identifiersare not within the damage data 77 at the time of making the comparison.The processor 440 can compare the crash data 75 to crash data ofmultiple collision events to determine more than one collision eventhaving similar crash data, and determine the PRCD from damage dataassociated with the multiple collision events determined to have similarcrash data.

The CRPI 460 can include program instructions to augment damage datawithin CADD to include PRCD confirmed to be RCD in the vehicleassociated with the CADD.

The CRPI 460 can include program instructions for generating acommunication to send a collision report, such as the collision report469, to an NCS, such as the NCS 24, 25, 26.

IV. Example Operation

Next, FIG. 5A shows a flowchart depicting a set of functions 500 (ormore simply “the set 500”) that can be carried out in accordance withthe example implementations described in this description. The set 500includes the functions shown in blocks labeled with whole numbers 501through 505. The following description of the set 500 includesreferences to elements shown in other figures described in thisdescription, but the functions of the set 500 are not limited to beingcarried out only by the referenced elements. A variety of methods can beperformed using all of the functions shown in the set 500 or any propersubset of the functions shown in the set 500. Any of those methods canbe performed with other functions such as one or more of the otherfunctions described in this description. A processor can perform orcause a function of the set 500 to be performed. That processor caninclude one or more processors.

In some example implementations, a scanner, such as the scanner 8, canperform one or more of the functions of the set 500, and one or more ofthose functions performed by the scanner 8 can be performed by theprocessor 40. In at least some of those implementations, the scanner 8can perform all of the functions of the set 500. The scanner 8 and theprocessor 40 can perform functions of the set 500 while the scanner 8 isoperatively connected to the vehicle 1 via the VCL 10. The connection ofthe scanner 8 and the vehicle 1 can include a wired connection, awireless connection, or a wired connection and a wireless connection.

In some other example implementations, the server 9 can perform one ormore of the functions of the set 500, and the one or more of thosefunctions performed by the server 9 can be performed by the processor440. In at least some of those implementations, the server 9 can performall of the functions of the set 500. The server 9 and the processor 440can perform functions of the set 500 while the server 9 is operativelyconnected to the scanner 8 via the network 11. Furthermore, in someother example implementations, the scanner 8 and the server 9 can bothperform one or more of the functions of the set 500. In at least some ofthose example implementations, the server 9 can provide the scanner 8with a display screen to display on the display 43.

This description describes a “main scanner menu” applicable to at leastsome example implementations. The processor 40 can output a displayscreen that includes the main scanner menu to the display 43 while thescanner 8 is transitioning to a power-on state or in response to thescanner 8 transitioning to the power-on state. Additionally oralternatively, the display 43 can display the main scanner menu in otheroperating states of the scanner 8. Examples of a display screenincluding a main scanner menu are shown in FIG. 6A and FIG. 11B.

Block 501 includes determining, by one or more processors, a vehiclemodel associated with a vehicle. Determining the vehicle model caninclude the processor 40, 440 receiving vehicle model informationindicative of the vehicle model. Determining the vehicle model can occurmanually, automatically, or partially manually and partiallyautomatically. Receiving the vehicle model information can occurmanually, automatically, or partially manually and partiallyautomatically.

Determining the vehicle model manually can occur in various ways. Forexample, determining the vehicle model manually can include theprocessor 40 outputting a display screen on the display 43 and receivingthe vehicle model information in response to a user selecting thevehicle model information from the display screen using user interfacecomponents of the scanner 8 while the display screen is displayed. Ifthe required vehicle model information is Y/M/M, the processor 40 canfirst output selectable years on the display screen, output theselectable make after a year selection is made via the display screen,and output the model after a vehicle make selection is made via thedisplay screen. If the required vehicle model information is Y/M/M/E,the processor 40 can output the display screen as described above forY/M/M and then output the selectable engine (i.e., ICE) on the displayscreen after a model selection is made via the display screen. FIG. 11Ashows a vehicle identification menu 169 in which a Y/M/M/E has beenselected via the vehicle identification menu 169.

As another example, determining the vehicle model manually can includethe processor 40 receiving vehicle model information entered via use ofthe multi-button keypad 84 or a touch screen of the display 43. Forinstance, the keys of the multi-button keypad 84 or the touch screencould be pushed in a sequence to enter the alpha-numeric characters“2017 Beta Tango 5.7L” (an example Y/M/M/E). The display 43 can displaythe entered characters in a display segment, such as the display segment178 shown in FIG. 11A. Determining the vehicle model manually caninclude the processor 40 determining the selector 117 (shown in FIG. 6B)is selected and causing the display 43 to display the display screen100.

Determining the vehicle model manually can typically be performedwithout error, although not always. For example, a user entering vehiclemodel information manually can enter incorrect vehicle modelinformation, such as by entering a VIN incorrectly or selecting anincorrect vehicle model attribute, such as an incorrect ICE identifier.Incorrectly entering vehicle model information can result misidentifyinga vehicle or having to repeat at least part of the process of manuallyentering the vehicle model information. Determining the vehicle modelautomatically overcomes the problems that can arise from manuallyentering vehicle model information incorrectly.

In one respect, determining the vehicle model automatically can occur inresponse to the scanner 8 being operatively connected to the vehicle 1with the scanner 8 operating in a power-on state, or in response tochanging a power state of the scanner 8 from a power-off state to thepower-on state while the scanner 8 is operatively connected to thevehicle 1. The display 43 can display the main scanner menu 109, 189while the processor 40 is determining the vehicle model informationautomatically in response to the scanner 8 changing to the power-onstate. In another respect, determining the vehicle model automaticallycan occur in response to the processor 40 receiving a selection toautomatically identify the vehicle model. As an example, receiving thatselection can include the processor 40 determining a selector 116 (shownin FIG. 6B) has been selected.

Automatically determining the vehicle model can include the processor 40selecting a first VDM protocol and a first VDM message to transmit tothe vehicle 1. The processor 40 can determine the first VDM message fromthe VDM 312 stored in the VRD 66. The processor 40 can cause the VCT 42to transmit or attempt to transmit the first VDM message using the firstVDM protocol to the vehicle 1. The VCT 42 can include a first integratedcircuit (IC) chip configured for transmitting VDM onto the VCL 10 andreceiving VDM transmitted on the VCL 10, in accordance with the firstVDM protocol.

If the processor 40 receives a VDM including vehicle model informationfrom the vehicle 1 in response to the first VDM message using the firstVDM protocol, the processor 40 can determine the vehicle model of thevehicle 1 from the vehicle model information. For example, the vehiclemodel information in the VDM can indicate an attribute of the firstvehicle, such as a VDM including at least a portion of a VIN associatedwith the first vehicle. In that case, the attribute can indicate a year,make, and model of the first vehicle. The processor 40 can store thedetermined vehicle model (regardless of how the processor 40 determinesthe vehicle model) and/or the vehicle model information in the vehiclemodel identifier 61. The processor 40 can determine the vehicle model ofthe first vehicle by determining an attribute of the vehicle modelinformation in the VDM matches a stored attribute of the vehicle model.The stored attribute of the vehicle model can be stored as part of theVRD 66.

If the processor 40 does not receive vehicle model information inresponse to transmitting or attempting to transmit the first VDM messageusing the first VDM protocol, the processor 40 selects a next VDMmessage to transmit or attempt to transmit to the vehicle 1 to requestvehicle model information. The next VDM message can be configured as aVDM message of the first VDM protocol or a second, different VDMprotocol. The VCT 42 can include a second integrated circuit (IC) chipconfigured for transmitting VDM onto the VCL 10 and receiving VDMtransmitted on the VCL 10, in accordance with the second VDM protocol.The processor 40 can repeat transmitting or attempting to transmit VDMmessages to request vehicle model information from the vehicle 1 untilthe processor 40 receives a response from the vehicle 1 includingvehicle model information or the processor 40 determines the scanner 8cannot automatically determine the vehicle model of the vehicle 1. Theprocessor 40 can determine the scanner 8 cannot automatically determinethe vehicle model of the vehicle 1 by determining the processor 40 hastransmitted each VDM of a set of vehicle model information request VDMstored in the VRD 66 and has not received the requested vehicleinformation from the vehicle 1.

Determining the vehicle model partially manually and partiallyautomatically can occur in various ways. The processor 40 can determinea mode for determining the vehicle model partially manually andpartially automatically by determining a selector from the displayscreen 91, such as the selector 118, 119, 120, was selected. The manualportion of determining the vehicle model can include using the capturedevice 45 to capture an image of the vehicle 1. The automatic portion ofdetermining the vehicle model can include determining the captured imagematches an image from the image 65, and determining the vehicle modelfrom vehicle model information associated with the image from the image65 that matches the captured image.

In response to determining the selector 118 was selected, the processor40 can activate the capture device 45. The display 43 can display thedisplay screen 92 as shown in FIG. 7A. The description of FIG. 7Adiscusses capturing an image of the VIN. The processor 40 canautomatically determine the vehicle model by determining a portion ofthe VIN shown in the image of the VIN matches vehicle model informationstored in the VRD 66.

In response to determining the selector 119 was selected, the processor40 can activate the capture device 45. The display 43 can display thedisplay screen 93 as shown in FIG. 7B. The description of FIG. 7Bdiscusses capturing an image of a vehicle and data identifying a view ofthe vehicle (e.g., front, rear, side or ICE). The processor 40 canautomatically determine the vehicle model by determining the view of thevehicle shown in the image of the vehicle matches a view of a vehicleshown in an image stored and/or referenced in the VRD 66 and fromvehicle model information associated with the image stored in the VRD66. The processor 40 can cause the display 43 to display a promptrequesting capture of a particular view of the vehicle connected to thescanner for comparison to other images stored in the VRD 66. Selectionof a virtual control and/or a key of the keypad 44 while the capturedevice 45 is active can cause the capture device to capture an image.

In response to determining the selector 120 was selected, the processor40 can activate the capture device 45. The display 43 can display thedisplay screen 94 as shown in FIG. 8A. The description of FIG. 8Adiscusses capturing an image of a license plate. The processor 40 canperform OCR on characters within the captured image. The processor 40can automatically determine the vehicle model by determining information(e.g., a license plate number, a geo-political state or countryidentifier) on the license plate shown in the image of the license platematches license plate information stored in the VRD 66, and determiningvehicle model information stored in the VRD 66 is associated with thelicense plate information stored in the VRD 66.

The processor 440 can determine the vehicle model associated with thefirst vehicle. The scanner 8 can transmit to the server 9 acommunication indicative of the vehicle model. This communication caninclude a vehicle model identifier that indicates the determined vehiclemodel. The server 9 can determine the vehicle model based on thecommunication from the scanner 8. The display 43 can display a displayscreen that shows the vehicle model identifier. Alternatively, thecommunication can include data indicative of the vehicle model, such asone or more image files of the first vehicle, from which the server 9can determine the vehicle model.

Next, block 502 includes determining, by the processor, a first DTC setwithin a first ECU in the vehicle. Determining the first DTC set withinthe first ECU can include the processor 40 and/or the VCT 42transmitting a VDM to request DTC data from the first ECU (e.g., the ECU3). The VDM to request the DTC data from the first ECU can includephysical addressing or functional addressing. The physically addressedVDM can include an OBD II VDM having a three byte header and a one bytemode number, where the first header byte identifies a priority of theVDM, the second header byte identifies a physical ID of the destination(i.e., the ECU 3), the third header byte identifies a physical ID of thesource (e.g., $F1 to represent the scanner 8), and the mode number is$03. The ID of the ECU 3 can depend on the type of the system in whichthe ECU 3 is installed and/or the VDM protocol used by the ECU 3. Thefunctionally addressed VDM can include a message using an eleven bitidentifier, a data length code byte, a number of additional data bytesbyte, and the mode number byte. Other examples of a VDM to request theDTC data are available.

Determining the first DTC set within the first ECU can include theprocessor 40 and/or the VCT 42 receiving a VDM including DTC data. TheVDM including DTC data can include an identifier of the first ECU and anidentifier of the first DTC. As an example, the DTC data can be arrangedaccording to the OBD II DTC format, in which the DTC data represents afirst character of the DTC as a letter selected from B, C, P, or U, andthe last four characters of the DTC as decimal numerals 0 to 9. Asanother example, the DTC data can be arranged according to a vehiclemanufacturer specific DTC format. The DTC data can include an identifierof one or more other DTC set by the first ECU.

The DTC data can, for some vehicle models, include drive cycleinformation indicating how many drive cycles of the vehicle haveoccurred with the vehicle since the first DTC was set within the firstECU. The drive cycle information can indicate a number of key cycles ofthe vehicle have occurred with the vehicle since the first DTC was setwithin the first ECU. The DTC data can include freeze-frame data storedin the first ECU. Freeze-frame data is data the ECU stores in responseto setting a DTC. The freeze-frame data can include PIDs and PID values.The freeze-frame data can include data captured by the ECU prior tosetting the DTC, data captured by the ECU at the time of setting theDTC, and/or data captured by the ECU after setting the DTC.

The processor 40 and/or the VCT 42 can request DTC data from multipleECU with the vehicle 1. The processor 40 can determine which ECU areinstalled in the vehicle 1 based on the VRD 66. If the processor 40cannot determine which ECU are installed in the vehicle 1 or otherwise,the processor 40 and/or the VCT 42 can transmit VDM with each potentialECU identifier and wait some amount of time for a response to each VDMto see if an ECU responds to the VDM request for DTC data. For example,if the vehicle 1 uses two byte physical addresses for its ECU, theprocessor 40 and/or the VCT 42 can transmit requests for DTC data withthe physical address $00 to $FF.

The processor 40 can request DTC from all ECU within the vehicle thatare configured to set a DTC in response to receiving a single selectionof a read DTC selector displayed on the display 43, such as a read DTCselector 110 (shown in FIG. 6A) or a read DTC selector 190 (shown inFIG. 11B). The processor 40 can cause the VCT 42 to transmit a VDM torequest codes from each ECU in the vehicle that sets DTC. In this way, atechnician can determine DTC from multiple ECU in the vehicle withouthaving to select each vehicle system on a vehicle scanner individuallyand then request the DTC stored in the ECU of that vehicle system, andrepeat those selection steps until performed for each vehicle system.Providing the ability to determine DTC from multiple ECU in the vehiclevia a single selector is an improvement over diagnostic tools thatrequiring selecting multiple vehicle systems individually to read DTCfrom multiple ECU in the vehicle.

The DTC data 62 can include each DTC identified in the received vehicleinformation. The DTC data 62 can include the other DTC data as well. Theprocessor 40 can cause the identified DTC to be added to a collisionreport 68. Determining the first DTC can occur as part of the processor40 performing a pre-repair scan of the vehicle as described elsewhere inthis description.

The processor 440 can determine the first DTC set within the first ECUin the first vehicle. The scanner 8 can transmit to the server 9 acommunication indicative of the first DTC. The server 9 can determinethe first DTC based on the communication from the scanner 8.

Next, block 503 includes determining, by the processor, a first damagedportion of the vehicle damaged by a collision. The scanner 8 cantransition to an operating state to determine the first damaged portionin response to any of a variety of trigger events. As an example, thetrigger event that causes the scanner 8 to transition to the operatingstate to determine the first damaged portion can include the processor40 determining a selector, such as the selector 113 of a main scannermenu 109 (shown in FIG. 6A) or a selector 191 of a main scanner menu 189(shown in FIG. 11B) is selected. A main scanner menu can be a top-levelmenu in a hierarchy of menus. A display screen that includes a mainscanner menu can be a main display screen. A main display screen can bea top-level display screen. A top-level menu or a top-level displayscreen can be referred to as a home menu or home display screen,respectively. The scanner 8 can display the main scanner menu whileoperating in a home display screen operating state.

In one or more implementations, the scanner 8 includes a single mode foridentifying damaged portion(s) of a vehicle. In at least some of theseimplementations, the display 43 can display a display screen forentering data and/or a selection to identify the damage portion(s) ofthe vehicle in response to detecting the aforementioned trigger event.In one or more other implementations, the scanner 8 includes multiplemodes for identifying damaged portion(s) of a vehicle. In at least someof these implementations, the display 43 can display a display screenhaving a damage selection menu from which a mode for identifying damageportion(s) of a vehicle can be selected.

As an example, the display 43 can display the display screen 104including a damage selection menu 220 (shown in FIG. 13A) whileoperating in the operating state to identify the damaged portion(s)(e.g., the first damaged portion) of the vehicle. The processor 440 cancause the display screen 104 and/or the damage selection menu 220 to betransmitted to the scanner 8 for displaying on the display 43. Theprocessor 40, 440 can determine a selection entered via the damageselection menu 220. As described below, the damage selection menu 220includes the selectors 221 to 226. Each of the selectors 221 to 226 isassociated with a different example mode for identifying damagedportion(s) of a vehicle.

Other example mode(s) for identifying damaged portion(s) of a vehicle inaddition to or as an alternative to one or more of the example modesshown in the damage selection menu 220 are possible. Moreover, in someimplementations, the damage selection menu 220 includes some, but notall, of the selectors 221 to 226, such as any one, any two, any three,any four, or any five of the selectors 221 to 226.

Next, a description of the example operating modes that can be enteredby making a selection from the damage selection menu 220 is provided. Inresponse to determining the selector 221 (shown in FIG. 13A) has beenselected, the processor 40 can cause the display 43 to display thedisplay screen 96 (shown in FIG. 9A), to receive a selection of avehicle image 150, 151, 152, and to cause the display 43 to display avehicle grid (such as the vehicle grid 134, 148 shown in FIG. 9B or 10A)showing the vehicle image 151, 152, 153 selected from the display screen96. Under some circumstances, such as when the processor 40 has alreadyidentified the vehicle 1, the processor 40 can cause the display 43 todisplay a vehicle grid, such as the vehicle grid 134, 148 withoutreceiving a selection of a vehicle image from the display screen 96.Under these example circumstances, the processor 40 can select anappropriate vehicle image from the image 65 to display in the vehiclegrid 134, 148 based on the vehicle identification.

The vehicle image selected for determining a damaged portion of thevehicle can include an image associated with the vehicle model or animage of a generic vehicle (e.g., as discussed with respect to FIG. 9A).The image is divided into multiple selectable portions. Each selectableimage portion corresponds to a reference vehicle portion of the vehiclemodel or the generic vehicle. Determining the first damaged portion ofthe vehicle can include receiving a selection of a selectable portion ofthe displayed image that corresponds to the first portion of the vehiclemodel or the generic vehicle. Receiving that selection can includedetermining that the touch screen of the display 43 displaying the imagewas touched at a location the selectable image is displayed.Additionally or alternatively, the cursor 89 and/or the keypad 44 couldbe used to select the selectable portion of the image. The processor canrefer to the vehicle image data 313 (shown in FIG. 16A) to determinethat the first portion is associated with the selected portion of thedisplayed image.

The processor can receive an input to switch vehicle images shown on thedisplay 43. Switching the images can include the processor 40 outputtinga different image of the vehicle model or the generic vehicle inresponse to receiving the input. As an example, in response to receivingthe input to switch vehicle images while an image showing a first sideof the vehicle model or the generic vehicle is being displayed, theprocessor can cause the display 43 to display an image showing a secondside of the vehicle model or the generic vehicle instead of the imageshowing the first side of the vehicle model or the generic vehicle.

Switching images shown on the display 43 allows a user to enter inputsindicating damage to different portion(s) of the vehicle model or thegeneric vehicle. Selecting damaged portion(s) from an image showing aparticular side of the vehicle can be critical as some vehiclecomponents are only located on the particular side of the vehicle modelor the generic vehicle. As an example, the first side of the vehicle 1can be a front of the vehicle 1, a rear of the vehicle 1, the left sideof the vehicle 1, a right side of the vehicle 1, a top side of thevehicle 1, or the bottom of the vehicle 1, and the second side of thevehicle 1 can be another of the front of the vehicle 1, the rear of thevehicle 1, the left side of the vehicle 1, the right side of the vehicle1, the top side of the vehicle 1, or the bottom of the vehicle 1.

Determining damaged portion(s) of a vehicle by selecting portion(s) of avehicle from a vehicle grid can be beneficial in that a user can selectportion(s) of a vehicle using a touch screen display or keypad and/orthe user can be confident that the processor is provided with correctselections of damage portion(s). Moreover, allowing a user to selectdamaged portion(s) of a vehicle allows the user to limit which damagedportion(s) of a vehicle are to be considered by the processor.

In response to determining the selector 222 (shown in FIG. 13A) has beenselected, the processor 40 can activate the capture device 45 to capturean image that shows the damaged portion(s) of the vehicle. The processor40 can cause the memory 47 to store the image showing the vehicle damageas part of the captured data 64 and/or the image 65. Capturing an imagefor use in determining damaged portion(s) of a vehicle can expedite thedetermination of the damaged portion(s) for at least one of thefollowing reasons: a user does not need to select damaged portions froma vehicle grid, and/or the captured image showing damage to a portion ofthe vehicle 1 can be compared to another image, such as image showingthe same portion of an identical vehicle model or an image showingdamage to the same portion of an identical vehicle model. Moreover,determining vehicle damage using images can be more consistent thandetermining damage based on user-selected input because different usersmay enter different amounts of deflection for two similarly damagedvehicles, whereas images of the two similarly damaged vehicles are morelikely to show the same amount of damage.

In response to determining the selector 223 (shown in FIG. 13A) has beenselected, the processor 40 can download an image showing a damagedportion of a vehicle. The processor 40 can cause the network transceiver41 to request and/or receive the image showing the damaged portion froma computing system, such as the server 9, or the NCS 24, 25, 26. Theprocessor 40 can cause the memory 47 to store the downloaded imageshowing the vehicle damage as at least part of the image 65. In analternative arrangement, the image showing the damaged portion can bedownloaded by the processor 40 prior to determining the selector 223 hasbeen selected. In this arrangement, determining the selector 223 hasbeen selected can cause the processor 40 to locate and receive thedownloaded image from the memory 47 for comparison to another image,such as an image of an undamaged portion of a vehicle associated withthe vehicle model.

In response to determining an image showing vehicle damage has beencaptured, downloaded, or otherwise received, the processor can determinethe first damaged portion based on the portion of the image showing thevehicle damage. The processor 40 can determine the first damaged portionby comparing the image showing the vehicle damage to an image of anundamaged vehicle associated with the vehicle model. The processor 40can receive the image of the undamaged vehicle from the image 65 and/orthe image library 465. If the image 65 does not include the image of theundamaged vehicle, the processor 40 can cause the network transceiver 41to request the image of the undamaged vehicle from the server 9. Therequest for the image of undamaged vehicle can include vehicle modelinformation indicative of the vehicle model associated with the vehicle1. Upon or after receiving the image of undamaged vehicle, the processor40 can cause the memory to store the image of undamaged vehicle in theimage 65 along with metadata indicative of the vehicle model shown inthe image of undamaged vehicle.

The processor 40 can cause the network transceiver 41 to transmit thecaptured image showing vehicle damage to the server 9 in a request fordetermining the first damaged portion of the vehicle damaged by acollision. The server 9 can determine the first damaged portion andtransmit a communication including data indicative of the first damagedportion to the network transceiver 41. Accordingly, the processor 40 candetermine the first damaged portion from the communication sent by theserver 9. As an example, determining damaged portion(s) of a vehiclefrom a downloaded image can be beneficial in situations in which thedamaged vehicle is not in proximity to the scanner 8.

In response to determining the selector 224 (shown in FIG. 13A) has beenselected, the processor 40 can cause the network transceiver 41 torequest and receive a repair order regarding the vehicle 1 from acomputing system, such as the server 9, or the NCS 24, 25, 26, and readthe repair order to determine the damaged portion of the vehicle 1. Therepair order can, for example, describe the first damaged portiontextually and/or graphically. The processor 40 can cause the memory 47to store the repair order. In some implementations, the processor 40 canperform OCR on the repair order to determine the first damaged portionfrom a textual description of the damaged location of the vehicle. Inanother implementation, the processor 40 can read the RO, such as an ROin the form of an XML file. In some implementations, the processor 40can determine markings made to a vehicle image on the repair order bycomparing the image on the repair order to an unmarked vehicle image anddetermine the first damaged portion pertains to a portion of the vehicleimage on the repair order marked with the marking. The repair order caninclude an estimate pertaining to the first vehicle and the collision.Alternatively, the processor 40 can cause the network transceiver 41 torequest and receive the estimate (separate from a repair order)regarding the vehicle and the collision from the NCS 24, 25, 26. Theprocessor 40 can perform OCR on the estimate to determine the firstdamaged portion from a textual description of the damaged location ofthe vehicle. As an example, determining damaged portion(s) of a vehiclefrom a repair order can be beneficial in situations in which the damagedvehicle is not in proximity to the scanner 8.

Determining a damaged portion of a vehicle from an RO can include theprocessor 40 comparing terms retrieved from the RO to one or moretaxonomies of terms. As an example, a taxonomy of terms can includespatial terms to indicate different portions of the vehicle 1. As anexample, a term “passenger side” and “driver side” can indicate eitherthe left side or the right side of the vehicle, depending on where thevehicle was built and/or where the vehicle is being driven. As anotherexample, a taxonomy of terms can include component terms to indicatedifferent components of the vehicle 1, such as “door”, “bumper”,“window”, “quarter panel,” among others.

In response to determining the selector 225 (shown in FIG. 13A) has beenselected, the processor 40 can display a text field for entering textdescribing a damaged portion of a vehicle via the keypad 44 or the touchscreen of the display 43. As an example, the display 43 can display amenu that includes spatial terms selectable via the keypad 44 as or toform the first vehicle portion identifier. As another example, thedisplay 43 can display a field in which text describing the firstvehicle portion identifier can be entered by pushing multiple buttons ofthe multi-button keypad 84.

In response to determining the first damaged portion, the processor 40can cause the memory 47 to store first damaged portion as the vehicleportion identifier 63 and/or to send to the server 9 a communicationincluding data indicative of the first damaged portion of the vehicle 1.

Depending on the extent of damage a vehicle sustained and how portionsof a vehicle are shown in a vehicle grid, determining a damaged portionof the vehicle can include determining multiple damaged portions of thevehicle from the vehicle grid.

In response to selecting the selector 226 (shown in FIG. 13A), theprocessor 40 can determine measurements of the vehicle 1 using one ormore laser transmitters and receivers. The processor 40 can generate anoutline of the vehicle 1 based on the measurements using the lasertransmitters and receivers and compare the outline of the vehicle 1 toone more images stored in the image 65. Differences between the outlineof the vehicle 1 and the one or more images showing similar portions ofvehicle 1 can indicate deflection of vehicle 1. The processor 40 can beconfigured to identify a deflected portion of a vehicle as a damagedportion of the vehicle. In an example implementation, the capture device45 can include the one or more laser transmitters and receivers. Theprocessor 40 can output a display screen showing damaged portions of avehicle, identified based on the measurements using the lasertransmitters and receiver. The display screens 735, 736 are examples ofthe vehicle grid 148 displaying damage areas 737, 738 that can bedetermined based on measurements using the laser transmitters andreceivers.

Once the processor 40 determines a damaged portion of vehicle 1, theprocessor 40 can, but need not necessarily, determine PIDs to requestfrom the vehicle 1, request and receive PID parameters for thosedetermined PIDs, and use the PIDs and PID parameters when making adetermination of whether the first DTC is collision-related.

Next, block 504 includes determining, by the processor, the first DTC iscollision-related. Determining the first DTC is collision-related caninclude determining, by the processor, the first damaged portion of thevehicle matches a reference vehicle portion associated with both acomponent attributable to setting the first DTC and the vehicle model.Determining whether a DTC is collision-related can provide for animproved user interface for documenting evidence related to repairing adamaged vehicle.

Moreover, determining whether a DTC is collision-related can provide theprocessor with information to determine which diagnostic procedure ofmultiple diagnostic procedures should be followed for diagnosing the DTCmore quickly. For example, if the DTC is determined to becollision-related, then the processor can select a diagnostic procedurethat is initially focused on diagnosing components located in thedamaged portions of the vehicle 1. On the other-hand, if the DTC isdetermined to be non-collision-related, then the processor can select adiagnostic procedure to diagnose the procedure that is initially focusedon non-damaged portions of the vehicle.

The VRD 66 can include reference data indicative of a vehicle referenceportion associated with a vehicle model and a DTC. If the memory 47 doesnot include that reference data for the vehicle model associated withthe first vehicle, the processor 40 can transmit to the server 9 arequest for reference data that can be used by the processor 40 todetermine whether the first DTC is collision-related ornon-collision-related. As an example, the request for reference data caninclude the vehicle model information of the vehicle 1 such that theserver 9 can provide the scanner 8 with reference data for making acollision-related determination regarding any DTC settable within thevehicle 1. As another example, the request for reference data caninclude the vehicle model information of the vehicle 1 and informationregarding a damaged portion of the vehicle (such as the first damagedportion) such that the server 9 can provide the scanner 8 with referencedata for making a collision-related determination regarding the DTCsettable within the vehicle 1 and a component attributable to settingthe DTC settable within the vehicle 1.

The component attributable to setting the first DTC can include to oneof the following vehicle components: an ECU, an input to an ECU, anoutput of an ECU, a sensor, a solenoid, a wire, a fiber optical cable, aconnector, a connector pin, an electrical ground circuit, an electricalpower line, a motor, a switch, or a signal line (e.g., a wire configuredto carry an electrical signal to or from an electrical vehiclecomponent). Other examples of the component attributable to setting thefirst DTC are available.

A determination that a DTC is collision-related or non-collision-relatedmay be made with a probability of less than one hundred percent. Theprocessor can make other determinations (e.g., a collision-relateddetermination) in order to increase the probability of correctlydetermining a DTC is collision-related or non-collision-related.Examples of other collision-related determinations are described below.

Another collision-related determination can include a determination ofwhether a difference in a first parameter from the vehicle 1 indicativeof the first DTC setting within the first ECU and a second parameterpertaining to a current operating state of the vehicle 1 is within athreshold range. In one example, the first and second parameters areboth indicative of a distance the vehicle 1 has been driven. In anotherexample, the first and second parameters are both indicative of a numberof driving cycles. In yet another example, the first and secondparameters are both indicative of a time. The processor can obtain theparameters indicating the distances, the numbers of driving cycles, orthe times by transmitting a parameter request including a PID associatedwith the distance, the number of driving cycles, or the time. Thethreshold range can be a number of miles for the distance parameters, anumber of drive cycles for the drive cycle parameters, and a time forthe time parameters.

Another collision-related determination can include a determination ofwhether a PID parameter for a PID associated with the first DTCindicates setting of the first DTC is collision-related. The scanner 8can determine the PID parameter from the vehicle 1. As an example, foran occurrence in which the first DTC is P0095, the scanner 8 candetermine parameter values $08, $78, $11, $5E, and $88 were stored forPID1, PID2, PID3, PID4, and PID5, respectively, at or in proximity to atime the collision occurred. The scanner 8 can request parameter valuesfor those PID since the PID parameter data 361 indicates those PID areassociated with the DTC P0095. The processor can compare the parametervalues determined from the vehicle 1 to PID parameter data 361. If allor most of the PID parameter values determined from the vehicle 1 areclose in proximity to the mean operating values for the associated PID,then the processor can be configured to determine the DTC is notcollision-related, but rather is set from a prior condition of thevehicle 1, such as normal wear of the vehicle 1.

FIG. 5B is a graph illustrating parameter value comparisons based on thePID parameter data 361 and the example parameter values for PID1, PID2,PID3, PID4, PID5. The PID parameter values are shown in FIG. 5B ashaving been normalized. FIG. 5B shows that PID1 deviates greatly withrespect to the mean operating parameter value for PID1. This tends toshow that the DTC (e.g., P0095) associated with the group of PIDs shownin FIG. 5B is collision-related since the parameter values have not agedequally. In particular, a vehicle component (e.g., a sensor) associatedwith the PID1 may have been damaged during a collision since the PID1parameter value received from the vehicle 1 deviates greatly from themean operating parameter value for PID1. On the other hand if all ormost the PID parameter values shown in FIG. 5B deviated from the meanoperating parameter values for those PIDs and are proximate the faultvalues for those PIDs, then the DTC would more likely not becollision-related.

An aged PID is a PID associated with PID parameters that indicate acomponent associated with the PID needs to be replaced or otherwiseserviced and/or performance of the component has degraded to a pointoutside a normal operating range. As an example, the component may beworn and/or have accumulated material such that the component cannotoperate within a normal (non-malfunctioning) operating range. Inparticular, the component associated with an aged PID can include anidle-air control valve, an exhaust gas recirculation (EGR) valve, a fuelinjector, an oxygen sensor, or a mass air flow sensor. In one respect,an aged PID may directly indicate the component. For example, theparameters of a PID that indicates signal values of an oxygen sensor mayindicate the oxygen sensor needs to be replaced or otherwise serviced.In another respect, an aged PID may indirectly indicate the component.For example, the parameters of a PID that indicate signal values of anoxygen sensor may indicate the EGR valve needs to be replaced orotherwise serviced. The indirect indication can arise from comparingparameters from multiple PIDs as shown in FIG. 5B.

If the vehicle 1 does not output a parameter for a requested PID oroutputs a parameter value for the requested PID that is at its maximumor minimum value and does not change over multiple requests for the PIDparameter, the processor 40 can be configured to determine that avehicle component (e.g., a sensor) associated with the PID and/or acircuit in between the vehicle component and an ECU is damaged, andpotentially collision-related.

Another collision-related determination can include a determination ofwhether the vehicle collision occurred before the first DTC was set. Theprocessor could make this determination by comparing a time or vehiclemileage when the first DTC was set to a time or vehicle mileage,respectively, when the first vehicle was involved in a collision.

Another collision-related determination can include a determination ofwhether a time the first DTC was set and a time the vehicle collisionoccurred are within a threshold amount of time. A determination that thefirst DTC set within the threshold amount of time can indicate a higherprobability of the first DTC setting as a result of the vehiclecollision. A determination that the first DTC did not set within thethreshold amount of time can indicate a lower probability of the firstDTC setting as a result of the vehicle collision. The threshold amountof time can depend upon various factors, such as the ECU that sets theDTC and/or the DTC itself. For instance, the threshold amount of timecan be greater for DTC set by a powertrain ECU as compared to a DTC setby a body control ECU. As an example, the threshold amount of time canbe an amount of time between zero and sixty seconds or a thresholdamount of time between zero and three hundred seconds. Moreover, thethreshold amount of time can be increased for vehicle collisionsinvolving multiple collisions, such as a first vehicle hitting a rearend of a second vehicle, and the rear end of the first vehicle being hitby a third vehicle thirty seconds after the first vehicle hit the secondvehicle. The threshold amount of time can include the amount of timebetween collisions plus a default threshold amount of time. Otherexamples of the threshold amount of time are available.

Another collision-related determination can include a determination ofwhether or not the first DTC is rarely set in vehicles associated withthe determined vehicle model. As an example, a DTC that sets in lessthan 0.05% of instances of servicing the vehicles of the determinedvehicle model can be considered to be rarely set. As another example, aDTC that sets in 15.0% of instances of servicing the vehicles of thedetermined vehicle model can be considered to be set often. Thepercentages of instances of the DTC setting can be based on mileage inthe vehicle. Accordingly, the processor can refer to a percentage of theDTC setting that is associated with a vehicle mileage matching thevehicle mileage of the damaged vehicle or being within a vehicle mileagerange including the vehicle mileage of the damaged vehicle. A DTC thatis set in the damaged vehicle, but rarely sets in vehicles of thedetermined vehicle model is more likely to be a DTC caused by thevehicle collision. A DTC that is set in the damage vehicle, but setsoften in vehicles of the determined vehicle model can be considered asless likely to be a DTC caused by the vehicle collision. The processor40 can determine the percentages of a DTC setting from the server 9. Theserver 9 can determine the percentages of the DTC setting based onrepair orders.

The processor can determine a second DTC is set in the vehicle 1. Thesecond DTC can be set by the same ECU that set the first DTC or by adifferent ECU in the vehicle. The processor can determine whether thesecond DTC is collision-related or non-collision-related. As an example,the processor can determine the second DTC is non-collision-related bydetermining that the second DTC was set prior to the collision. Asanother example, the processor can determine the second DTC isnon-collision-related by determining the first damaged portion of thevehicle 1 is not associated with any vehicle component associated withsetting the second DTC. The collision report 68 can include anidentifier of the second DTC, such as the non-collision-related DTC data520 shown in FIG. 17.

Next, block 505 includes outputting, by the processor, a collisionreport that indicates the first DTC is collision-related. The processor40 can generate and store the collision report in the memory 47 as thecollision report 68.

The collision report 68 can be output to a variety of devices. Forexample, outputting the collision report 68 can include the processor 40outputting the collision report 68 to one or more of the following: thenetwork transceiver 41, the display 43, the server 9, the NCS 24, 25,26, the collision service provider 17, the insurance company 18, 19, 20,or a printer (e.g., other computing systems 670 shown in FIG. 19). Acollision report output to the network transceiver 41 can be output bythe network transceiver 41 to the network 11 for transmission to one ormore of the following: the network transceiver 41, the display 43, theserver 9, the NCS 24, 25, 26, the collision service provider 17, theinsurance company 18, 19, 20, or a printer (not shown). A collisionreport output to the display 43 can be displayed by the display 43.

Another function that can be performed by the processor 40 incombination with a described method that includes performing the set 500includes the processor 40 performing a pre-repair scan of the vehicle 1to determine which DTC are set in the vehicle 1 prior to a portion ofthe vehicle damaged by the collision being repaired. The processor 40can cause the DTC determined by the pre-repair scan to be stored as partof the DTC data 62 and/or the collision report 68. The pre-repair scancan occur after the processor 40 determines the vehicle model. Thepre-repair scan can occur automatically upon the processor 40determining the vehicle model associated with the vehicle while thescanner is connected to the vehicle and the vehicle is powered on. TheDTC determined during a pre-repair scan can be included in the collisionreport 68 output by the processor 40.

Another function that can be performed by the processor 40 incombination with a described method that includes performing the set 500includes the processor 40 performing a post-repair scan of the vehicle 1to determine which DTC are set in the vehicle 1 after the portion of thevehicle damaged by the collision was repaired. The processor 40 cancause the DTC determined by the post-repair scan to be stored as part ofthe DTC data 62 and/or the collision report 68. The post-repair scan canoccur after the processor 40 determines the vehicle model. Thepost-repair scan can occur in response to receiving a request to performthe post-repair scan while the scanner is connected to the vehicle andthe vehicle is powered on. The DTC determined during a post-repair scancan be included in the collision report 68 output by the processor 40.

Performing the pre-repair scan and the post-repair scan is beneficialbecause the processor 40 can compare the DTC determined during thepre-repair scan to the DTC (if any) determined during the post-repairscan to determine if any DTC set are sent in the vehicle after thepre-repair scan. DTC set in the vehicle after the pre-repair scan canindicate that some repair was performed incompletely or incorrectly(e.g., a DTC can be indicative of an electrical connector in the vehiclebeing disconnected).

Another function that can be performed by the processor 40 incombination with a described method that includes performing the set 500includes the processor 40 determining a warning regarding repairing thevehicle, outputting the warning to the display, and the display 43displaying the warning. Determining the warning can include theprocessor 40 determining the warning is mapped to the reference portionassociated with the vehicle model, such as the warning 360 mapped to thereference portions LRQ, RRQ, LR, and RR.

Another function that can be performed by the processor 40 incombination with a described method that includes performing the set 500includes the processor 40 receiving an input indicative of a vehicleadjustment selector (e.g., the selector 192 shown in FIG. 11B) beingselected. In response to receiving that input, the processor 40 canoutput and the display 43 can display vehicle adjustment functioninformation and a vehicle adjustment function selector. FIG. 12A showsan example of vehicle adjustment function information regarding a DTCC0040. FIG. 13B shows an example of vehicle adjustment functioninformation including multiple vehicle adjustment function selectors.The processor 40 can receive an input indicative of a vehicle adjustmentfunction selector being selected and outputting a signal orcommunicating to perform a vehicle adjustment corresponding to theselected vehicle adjustment function selector. As an example, thevehicle adjustment includes one or more of the following: programming avehicle component in the first vehicle, initializing a vehicle componentin the first vehicle, calibrating a vehicle component in the firstvehicle, or resetting a vehicle component in the first vehicle.

Another function that can be performed by the processor 40 incombination with a described method that includes performing the set 500includes the processor 40 receiving an input indicative of a DTC (e.g.,a DTC in the list of DTC 133 shown in FIG. 8B) being selected. Inresponse to receiving that input, the processor 40 can output and thedisplay 43 can display additional information regarding a DTC set in theECU 3 in the vehicle 1. For instance, the additional informationregarding a DTC can include the DTC information 195 pertaining to theDTC C0040 shown in FIG. 12A if the DTC C0040 was selected from the listof DTC 133.

Another function that can be performed by the processor 40 incombination with a described method that includes performing the set 500includes the processor 40 determining that a DTC set in the vehicle is aDTC indicative of a fault and/or deployment of a deployable vehiclesafety restraint system (SRS) component, such as an air bag or a seatbelt retractor pre-tensioner. The processor 40 can be configured to addsuch DTC to the collision report 68 even though the deployable SRScomponent may not located in proximity to the vehicle's point-of-impact.

V. Example Collision Report

Next, FIG. 17 shows example information that can be included within thecollision report 68. As shown in FIG. 17, the collision report 68includes a shop identifier 510, a technician identifier 511, a vehiclemodel identifier 512, a customer name 513, a customer insurance companyidentifier 514, repair date(s) 515, a collision date 516, a collisiontime 517, a collision-related DTC data 518, a DTC set time 519, anon-collision-related DTC data 520, a DTC set time 521, repair part costinformation 522, collision images 523, labor rate and time information524, and a cost estimate 525 (e.g., a sum of the repair part costinformation 522 and labor cost based on the labor rate and timeinformation 524). The time 519 is indicative of when the first DTC wasset with respect to the collision time 517. The processor 40 can receivethe collision time 517 from a VDM the processor 40 requests and receivesfrom an SRS ECU. The processor 40 can receive the DTC set time 519 froma VDM the processor 40 requests and receives from the ECU that set thefirst DTC.

The repair part cost information 522 can include part information basedon a selection made via a display screen, such as the display screen 850shown in FIG. 15K. The processor 40, 440 can, but need not necessarily,determine a price for a vehicle component from the VRD 66, 466.

Furthermore, some portion or an entirety of the collision report 68 canbe formatted according to an industry standard. As an example, someportion or an entirety of the collision report 68 can be formatted basedon an industry standard defined by CIECA (Collision Industry ElectronicCommerce Association), Northbrook, Ill., such as the CIECA BusinessMessage Suite (BMS), version 5.6.0, October 2017, which is incorporatedherein by reference. In particular, the collision report 68 can, butneed not necessarily, include an SGML (standard generalized markuplanguage) or XML (extensible markup language) tag and associated datadefined by that CIECA BMS. As another example, the industry standardupon which the collision report or some portion of the collision report68 is based can, but need not necessarily, include (1) the CIECA RepairOrder Folder Service XML Implementation Guide, Appendix C, BusinessUsage FAQs, Release 2009R2, October 2009, which is incorporated hereinby reference, (2) CIECA Attachment XML Service, XML ImplementationGuide, Appendix C, Business Use Cases and Standard XML ImplementationExamples, Release 2004R2, November 2004, which is incorporated herein byreference, (3), CIECA Scan Services XML Implementation Guide, Release2017R2, October 2017, which is incorporated herein by reference, and/or(4) CIECA SCAN Messages, XML Implementation Guide, Appendix C, BusinessUsage FAQs, Release 2017R2, October 2017, which is incorporated hereinby reference.

Furthermore still, some portion or an entirety of the collision report68 can be forwarded to an NCS, such as the NCS 24. As an example, aportion of the collision report 68 including part numbers can includethe part numbers formatted according to the industry standard.

VI. Example Display Screens and Keypad

Next, FIG. 6A to FIG. 15N depict example implementations of the scanner8, the display 43, and the keypad 44. The display 43 can include a touchscreen, such as a capacitive, resistive, or infrared touch screen. Thecapacitive touch screen can be surface capacitive or projectivecapacitive. The processor 40 can provide a display screen to the display43. The display 43 can display the display screen received by thedisplay 43. Examples of a display screen are shown in FIG. 6A to FIG.15N. In some implementations, the scanner 8 receives a display screenfrom the server 9 and the display 43 displays the display screenreceived from the server 9 using a browser application. In otherimplementations, the processor 40 generates the display screen andprovides the display screen to display 43.

The processor 40 can detect an input or selection entered using thetouch screen. For instance, the processor 40 can detect a touch screeninput such as a tap input (e.g., one finger touching the touch screen),a pinching input (e.g., two fingers touching the touch screen beingbrought closer to each other), a spreading input (e.g., two fingerstouching the touch screen moved farther apart from each other), or aswiping input (e.g., one finger moving from one point to a second pointon the touch screen). Other examples of touch screen inputs areavailable. The processor 40 can also detect an input or selectionentered using the keypad 44.

In some implementations of the keypad 44, such as the implementationsshown in FIG. 6A to FIG. 15E, the keypad 44 can include a directionalkeypad 80 for selecting up, down, left and right movements orselections, a yes button 81 selectable to signify a selection of yes, ano button 82 selectable to signify a selection of no, a power button 83,a multi-button keypad 84, and buttons 85, 86, 87, and 88. Themulti-button keypad 84 can include a set of numeric keys, alpha-numerickeys, alphabet keys, or keys for entering some other combinations ofletters, numbers, or symbols (e.g., punctuation symbols). A button, suchas the button 85, 86, 87, 88, can be a reconfigurable button conditionedon a selector displayed on the display 43 in proximity to the button.

In other implementations of the keypad 44, such as the implementation ofthe scanner 8 and the keypad 44 shown in FIG. 15F, the keypad 44 hasfewer keys as compared to the implementation of the keypad 44 shown inFIG. 6A to FIG. 15E. In FIG. 15F, the keypad 44 include the directionkeypad 80, the yes button 81, the no button 82, and the power button 83.The touch screen of the display 43 can be used to input a selection orinput described as being performed by selection of a button 85, 86, 87,88 or the multi-button keypad 84. Moreover, the display 43 could beconfigured with portions of the touch screen to represent (a) selectionsof up, down, left and right movements or selections similar to thoseselectable using the directional keypad 80, (b) a selection of yessimilar to the selection selectable using the yes button 81, or (c) aselection of no similar to the selection selectable using the no button82. Any display screen shown in FIG. 6A to FIG. 15E can be displayedusing a touch screen within the implementation of the scanner 8 shown inFIG. 15F.

Returning to FIG. 6A, this figure also depicts a display screen 90displayed on the display 43. A cursor 89 is displayed by the display 43in FIG. 6A and in other figures. The cursor 89 can be positioned by useof the directional keypad 80, for example. The cursor 89 can bepositioned on a selector displayed on the display 43. A button on thekeypad 44, such as the button 85, can be pushed while the cursor 89 ispositioned on or in proximity to the selector to indicate the selectorhas been selected.

The display screen 90 includes the main scanner menu 109. The processor40 can output the main scanner menu 109 in response to a variety ofevents, such as powering on the scanner 8 via the power button 83 or aselection to return to the main scanner menu 109 while the display 43 isdisplaying a different display screen. The main scanner menu 109includes the read DTC selector 110 (shown as “READ DTC”) selectable tocause the scanner 8 to transition to an operating state in which thescanner 8 operates to determine DTC set by the ECU 3 in the vehicle 1.The processor 40 can determine whether a DTC set by the ECU 3 iscollision-related. The main scanner menu 109 includes a selector 111(shown as “COLLISION ESTIMATOR”) selectable to cause the scanner 8 totransition to an operating state in which the scanner 8 operates todetermine data for preparing a collision estimate and/or to determine acollision estimate. The main scanner menu 109 includes a selector 112(shown as “COLLISION PROCEDURES”) selectable to cause the scanner 8 totransition to an operating mode in which the scanner 8 obtains anddisplays a collision procedure. The main scanner menu 109 includes aselector 113 (shown as “DAMAGE IDENTIFICATION”) selectable to cause thescanner 8 to transition to an operating state in which the scanner 8determines information regarding a damaged vehicle, such as a damagedportion at which the vehicle is damaged. The main scanner menu 109includes the squib status selector 114 (shown as “SQUIB STATUS”)selectable to cause the scanner 8 to programmatically check the statusof an SIR system squib.

Next, FIG. 6B also depicts a display screen 91 displayed on the display43. The display screen 91 includes an enter vehicle model informationmenu 115. The processor 40 can output the enter vehicle modelinformation menu 115 in response to a variety of events, such asselection of the read DTC selector 110 or selector 111, 112, 113. As anexample, the enter vehicle model information menu 115 includes aselector 116 selectable to cause the scanner 8 to transition to anoperating state in which the scanner 8 determines vehicle modelinformation regarding the vehicle 1 by transmitting and/or receiving aVDM including data indicative of the vehicle model or data from whichthe vehicle model can be derived. The ECU 3 can transmit a VDM includingdata indicative of the VIN or at least a part of the VIN associated withthe vehicle 1. As another example, the enter vehicle model informationmenu 115 includes a selector 117 selectable to cause the scanner 8 totransition to an operating state in which the scanner 8 determinesvehicle model information regarding the vehicle 1 from user interfacecomponents (e.g., the display 43 and the keypad 44) of the scanner 8. Asanother example, the enter vehicle model information menu 115 includes aselector 118 selectable to cause the scanner 8 to transition to anoperating state in which the scanner 8 determines vehicle modelinformation regarding the vehicle 1 via capturing an image of thevehicle's VIN. As another example, the enter vehicle model informationmenu 115 includes a selector 119 selectable to cause the scanner 8 totransition to an operating state in which the scanner 8 determinesvehicle model information regarding the vehicle 1 by capturing an imageshowing at least a portion of the vehicle's body. As another example,the enter vehicle model information menu 115 includes a selector 120selectable to cause the scanner 8 to transition to an operating state inwhich the scanner 8 determines vehicle model information regarding thevehicle 1 by capturing an image of the vehicle's license plate.

Next, FIG. 7A also depicts a display screen 92 displayed on the display43. The display screen 92 shows a VIN label 125 displayed on the display43. The display screen 92 can be displayed in response to selection ofthe selector 118 shown in FIG. 6B. The capture device 45 can provide theprocessor 40 and/or the display 43 the data representing light sensed byan image sensor of the capture device 45. The button 85 can beconfigured as a shutter button for the capture device 45 when thedisplay screen 92 is displayed. The display screen 92 is showndisplaying a reconfigurable button label 126 indicating that a currentconfiguration of the button 85. Pressing the button 85 can cause theprocessor 40 to store an image of the VIN label 125 within the captureddata 64. The processor 40 can be configured to determine the VINrepresented by the VIN label 125, for example, by performing opticalcharacter recognition of the characters shown on the VIN label 125 or bydecoding the bar code shown on the VIN label 125. The determined VIN canbe stored as the vehicle model identifier 61.

Next, FIG. 7B also depicts a display screen 93 displayed on the display43. The display screen 93 shows a vehicle and reconfigurable buttonlabels 128, 129, 130, and 131 indicating current configurations of thebuttons 85, 86, 87, and 88. The buttons 85, 86, 87, and 88 can beconfigured as shutter buttons for the capture device 45 when the displayscreen 93 is displayed. The display screen 93 can be displayed inresponse to selection of the selector 119 shown in FIG. 6B. Pressing thebutton 85 can cause the processor 40 to store (within the captured data64 for identifying the vehicle model) an image of the vehicle 127displayed on the display 43 and data indicating that stored image showsa front of the vehicle 1. Pressing the button 86 can cause the processor40 to store (within the captured data 64 for identifying the vehiclemodel) an image of the vehicle 127 displayed on the display 43 and dataindicating that stored image shows a rear of the vehicle 1. Pressing thebutton 87 can cause the processor 40 to store (within the captured data64 for identifying the vehicle model) an image of the vehicle 127displayed on the display 43 and data indicating that stored image showsa side (e.g., right side or left side) of the vehicle 1. Pressing thebutton 88 can cause the processor 40 to store (within the captured data64 for identifying the vehicle model) an image of the vehicle 127displayed on the display 43 and data indicating that stored image showsan ICE of the vehicle 1.

Next, FIG. 8A also depicts a display screen 94 displayed on the display43. The display screen 94 shows a license plate 132 displayed on thedisplay 43. The display screen 94 can be displayed in response toselection of the selector 120 shown in FIG. 6B. The capture device 45can provide the processor 40 and/or the display 43 the data representinglight sensed by an image sensor of the capture device 45. The button 85can be configured as a shutter button for the capture device 45 when thedisplay screen 94 is displayed. The display screen 94 is showndisplaying a reconfigurable button label 126 indicating that a currentconfiguration of the button 85. Pressing the button 85 can cause theprocessor 40 to store an image of the license plate 132 within thecaptured data 64. The processor 40 can be configured to determine avehicle model associated with the license plate 132, for example, byperforming optical character recognition of the characters shown on thelicense plate 132 and performing a query of a database of vehicle modelsand license plate information. The vehicle model determined from thelicense plate 132 can be stored as the vehicle model identifier 61.

Next, FIG. 8B also depicts a display screen 95 displayed on the display43. The display screen 95 includes a list of DTC 133 set in the vehicle1. The list of DTC 133 can indicate all DTC currently set within thevehicle 1. At a time the list of DTC 133 is displayed, the processor 40may not have determined whether or not each DTC in the list of DTC 133is collision-related. The display screen 95 can be displayed after theprocessor 40 determines the vehicle model associated with the vehicle 1.The processor 40 can refer to the VRD 66 to determine a VDM protocol forcommunicating with the ECU 3 and an identifier of the ECU 3. Theprocessor 40 can transmit a VDM or cause the VCT 42 to transmit a VDM torequest DTC data from the ECU 3. The processor 40 and/or the VCT 42 canreceive a VDM including DTC data from the ECU 3.

The DTC within the list of DTC 133 include a letter prefix, such as Bfor body system DTC and C for chassis system DTC. Other letter prefixesthat could be used include P for powertrain DTC and U for network DTC.The DTC within the list of DTC 133 include four numbers after the letterprefix. In other examples, a DTC may not include a letter prefix, Inparticular, DTC B0051 represents an air bag deployment commanded DTC,DTC B05020 represents a rear discharge temperature sensor malfunctionDTC, the DTC C0040 represents a right front wheel speed circuitmalfunction DTC, the DTC C0070 represents a right front ABS solenoid #1circuit malfunction DTC, the B1182 DTC represents a TPMS right frontmalfunction, and the DTC C0085 represents a left rear ABS solenoid #2circuit malfunction DTC. In other examples, a DTC may include adifferent number of numbers to designate a DTC. In still other examples,a DTC can be indicated by some other manner. The list of DTC 133includes a textual description of each of the DTC included in the listof DTC 133.

The display screen 95 includes a selector 78 selectable to cause theprocessor 40 and/or the VCT 42 to transmit a VDM to the ECU 3 requestingthe ECU 3 to clear the DTC (e.g., erase the DTC within the ECU 3). Ifthe list of DTC 133 includes DTC set by more than one ECU, selecting theselector 78 can cause the processor 40 and/or the VCT 42 to transmit aVDM to each ECU within the vehicle 1 requesting that ECU to clear itsDTC or to transmit a VDM to each ECU within the vehicle that isrepresented in the list 133 as having a DTC set.

The display screen 95 includes a selector 79 selectable to cause theprocessor 40 to add the DTC determined for the list of DTC 133 to thecollision report 68 regarding the vehicle 1. If the collision report 68has not been generated yet, the processor 40 generates the collisionreport 68 including the DTC determined for the list of DTC 133.

Next, FIG. 9A also depicts a display screen 96 displayed on the display43. The display screen 96 shows vehicle images 150, 151, and 152selectable for displaying in one or more vehicle grids to select adamaged portion indicative of a spatial location on a vehicle damaged bya collision. The vehicle images 150, 151, and 152 are selectable bypushing button 85, 86, 88, respectively. The vehicle images 150, 151,and 152 can be stored in the image 65. The vehicle images 150, 151, and152 can be generic vehicle images representing a particular body style,such as a two door car, a four door car, a two door pickup truck, a fourdoor pickup truck, or a passenger van. As an example, the vehicle image150 can be displayed to represent two door cars, the vehicle image 151can be displayed to represent four door cars, and the vehicle image 152can be displayed to represent two door pickup trucks. The vehicle images150, 151, 152 can include rotatable images such that other views of thevehicle can be displayed, such as a front view, a rear view, a left sideview and a right side view.

The two door vehicle shown in the vehicle image 150 most closelyresembles the vehicle 1. Accordingly, the processor 40 can output avehicle grid including the vehicle image 150 in response to determiningthe button 85 is pressed while the display screen 96 is displayed. Thevehicle image displayed in the grid can be a top view of the genericvehicle or another view of the generic vehicle. Other examples of ageneric vehicle that can be represented by a vehicle image fordisplaying in a grid are available. Additionally or alternatively, thevehicle images 150, 151, 152 can be images of particular vehicle models.

Next, FIG. 9B also depicts a display screen 97 displayed on the display43. The display screen 97 includes a vehicle grid 134 showing a vehicle.The processor 40 can output the display screen 97 to allow a user toselect a portion of a vehicle damaged by a collision. In one respect,the vehicle grid 134 shows a generic vehicle image that representsmultiple vehicle models including and similar to the vehicle modelassociated with the vehicle 1. The generic vehicle image can, forexample, include an image of a 2-door car (see, the vehicle image 150 inFIG. 9A), a four-door car (see, the vehicle image 151 in FIG. 9A), or apickup truck (see, the vehicle image 152 in FIG. 9A). In anotherrespect, the vehicle grid 134 shows an image of a vehicle of the vehiclemodel associated with the vehicle 1. A vehicle image shown in thevehicle grid 134 can, for example, include a wireframe image or aphotographic image. The vehicle image shown in the vehicle grid 134 caninclude a two-dimensional image or a three-dimensional image.

Any example display screen shown in the drawings can, but need notnecessarily, include a next selector 147 to advance to a next displayscreen and/or a back selector 149 to return to a prior display screen.Selection of the next selector 147 can include the processor 40, 440processing any inputs made via another selector from that display screenprior to selection of the next selector 147. For clarity of thedrawings, the next selector 147 and the back selector 149 are not shownin all of the drawings. The next selector 147 shown on the displayscreen 97 can be configured to indicate that selecting a damaged portionis complete.

The vehicle grid 134 includes multiple vehicle grid locations. Table 2shows example names of damaged portions associated with example vehiclegrid locations shown in FIG. 9B. The cursor 89 can be positioned on avehicle grid location, such as the vehicle grid location 136, and abutton, such as the Yes button 81 can be pressed to select the vehiclegrid location to identify a portion of the vehicle damaged by acollision. If the display 43 includes a touch screen, the processor 40can determine the portion of the vehicle damaged by a collision bydetermining the vehicle grid location (associated with the damagedportion) displayed on the display 43 is touched. The keypad 44 caninclude a button (e.g., the directional keypad 80) to rotate the vehiclegrid 134 along multiple axes. In FIG. 9B, the vehicle grid 134 shows aplan view of the vehicle. Rotation of the vehicle grid 134 can result inthe vehicle grid showing a different view of the vehicle, such as afront view, back view, right side view left side view, or undersideview.

TABLE 2 Vehicle Grid Vehicle Location portion Vehicle Component DTCSymptom Image 135R Right Front Null Null Null VM1_135R.jpg 136R RightFront RF WSS C1164 ABS RF inop. VM1_136R.jpg Quarter RF TMPS C1264 TPMSRF inop. 137R Right A to B RF window B0211 RF window VM1_137R.jpg Pillarmotor inop. 138R Right B to C RR window B0212 RR window VM1_139R.jpgPillar motor inop. 139R Right Rear RR WSS C1165 ABS RR inop.VM1_135R.jpg Quarter RR TMPS C1265 TPMS RR inop. 140R Right Rear Rt.tail light Null Rt. tail light inop. VM1_140R.jpg 135C Center Front SIRsensor #1 C0333 Null VM1_135C.jpg 136C Center Front Radiator, coolingP0118 Leaking VM1_136C.jpg Quarter fan, Fuel injectors P0201 coolant,engine #1-6, spark plugs P0202 overheating, #1-6, intake P0203 Enginemisfire manifold, electric P0204 cylinders #1-6, starter flywheel, P0205engine does coil pack. P0206 not start 137C Center A to B Null Null NullVM1_137C.jpg Pillar 138C Center B to C Null Null Null VM1_139C.jpgPillar 139C Center Rear CHMSL Null CHMSL inop. VM1_135C.jpg Quarter 140CCenter Rear License plate Null License plate VM1_140C.jpg lights lightsinop 135L Left Rear Lt. tail light Null Lt. tail light inop.VM1_135L.jpg 136L Left Rear LR WSS C1166 ABS LR inop. VM1_136L.jpgQuarter LR TMPS C1266 TPMS LR inop. 137L Left B to C LF window B0213 LFwindow VM1_137L.jpg Pillar motor inop. 138L Left A to B LR window B0214LR window VM1_139L.jpg Pillar motor inop. 139L Left Front LF WSS C1167ABS LF inop. VM1_135L.jpg Quarter LF TMPS C1267 TPMS LF inop. 140L LeftFront Null Null Null VM1_140L.jpg

In at least some implementations, a vehicle grid displayed on thedisplay 43 can show one or more vehicle grid locations as being selectedprior to a user selecting a vehicle grid location (i.e., pre-selected).As an example, the processor 40 can determine that DTC C1165 and DTCP0118 are set in the vehicle 1. Advantageously, by referring to vehiclereference data, such as vehicle reference data shown in FIG. 2, theprocessor 40 can determine that vehicle grid location 139R is associatedwith DTC C1165 and the vehicle grid location 136C is associated with DTCP0118 and responsively show vehicle grid locations 136C and 139R asbeing selected. A user can confirm whether or not vehicle damage existsat the selected vehicle grid locations. For example, the user can entera selection indicating that the portion of the vehicle shown in thevehicle grid location 136C is not damaged. The processor 40 can use suchselection to classify DTC P0118 as not being collision related. Asanother example, the user can enter a selection indicating that theportion of the vehicle shown in the vehicle grid location 139R isdamaged. The processor 40 can use such selection to classify DTC C1165as being collision related.

Next, FIG. 10A also depicts a display screen 98 displayed on the display43. The display screen 98 shows a vehicle grid 148. The vehicle grid 148shows a right side of the vehicle 1 and additional grid locations. Table3 shows example damaged portion names associated with example vehiclegrid locations shown in FIG. 10A. A vehicle grid positon of the vehiclegrid 148 can be selected using the display 43 and/or the keypad 44. Somegrid locations, such as the grid location 146 UR, may not include anyportion of the vehicle image. The other views of a vehicle, such as thefront view, the back view, the left side view, and the underside viewcan also be shown on the display 43 within a grid.

TABLE 3 Vehicle Grid Location Vehicle portion 141 UR Upper Right Front141 MR Middle Right Front 141 LR Lower Right Front 142 UR Upper RightFront Quarter 142 MR Middle Right Front Quarter 142 LR Lower Right FrontQuarter 143 UR Upper Right A to B Pillar 143 MR Middle Right A to BPillar 143 LR Lower Right A to B Pillar 144 UR Upper Right B to C Pillar144 MR Middle Right B to C Pillar 144 LR Lower Right B to C Pillar 145UR Upper Right Rear Quarter 145 MR Middle Right Rear Quarter 145 LRLower Right Rear Quarter 146 UR Upper Right Rear 146 MR Middle RightRear 146 LR Lower Right Rear

As another example, each vehicle grid location can be associated with aseparate body panel of the vehicle 1. For a four door automobile, thebody panels can include a hood (sometime referred to a bonnet), a leftfront wing, a right front wing, a left front door, a right front door, aleft rear door, a right rear door, a left back wing, a right, and aright back wing, and a tailgate. For a two door automobile, the bodypanels can include a hood, a left front wing, a right front wing, a leftdoor, a right door, a left back wing, a right, and a right back wing,and a tailgate.

Next, FIG. 10B also depicts a display screen 99 displayed on the display43. The display screen 99 shows a list of collision-related DTC 161 anda list of non-collision-related DTC 162. Those lists can be displayed inresponse to the processor 40 determining the selector 79 was selected.The DTC shown in the list of collision-related DTC 161 and the list ofnon-collision-related DTC 162 can be selected individually or as acombination of two or more DTC to cause the scanner 8 to display furtherdetails regarding the selected DTC(s). FIG. 12A shows a display screen102 that displays further details regarding the DTC C0040.

Next, FIG. 11A also depicts a display screen 100 displayed on thedisplay 43. The display screen 100 shows a vehicle identification menu169. The processor 40 can output the vehicle identification menu 169 inresponse to determining the selector 117 (shown in FIG. 6B) wasselected. The vehicle identification menu 169 can provide sub-menus fromwhich a variety of vehicle model attributes are selectable. FIG. 11Ashows a sub-menu 170 for selecting a vehicle model year attribute andthe vehicle model year attribute 171 indicative of an example model year“2017” being selected. FIG. 11A shows a sub-menu 172 for selecting avehicle make attribute and the vehicle make attribute 173 indicative ofan example vehicle make “Beta” being selected. The content of thesub-menu 172 can be conditioned on the vehicle model year attributeselected from the sub-menu 170. FIG. 11A shows a sub-menu 174 forselecting a vehicle model attribute and the vehicle model attribute 175indicative of an example vehicle model “Tango” being selected. Thecontent of the sub-menu 174 can be conditioned on the vehicle makeattribute selected from the sub-menu 172 and on the vehicle model yearattribute selected from the sub-menu 170. FIG. 11A shows a sub-menu 176for selecting an ICE attribute and the ICE attribute 177 indicative ofan example ICE “5.7 L” being selected. The content of the sub-menu 176can be conditioned on the vehicle model selected from the sub-menu 174,the vehicle make attribute selected from the sub-menu 172, and on thevehicle model year attribute selected from the sub-menu 170. The cursor89 can be used select options from the vehicle identification menu 169and the sub-menus 170, 172, 174, and 176. The vehicle identificationmenu 169 can include sub-menus for selecting other vehicle modelattributes. FIG. 11A shows a display segment 178 displaying the vehiclemodel identifier 179 entered manually. The vehicle model identifier 179in the display segment 178 can appear as a result of selecting vehiclemodel attributes from the sub-menus 170, 172, 174, and 176 or inresponse to pushing a sequence of keys on the multi-button keypad 84.The display segment 178 can display a vehicle model attribute, such asthe vehicle year, prior to receiving all vehicle model attributes thatmake up the vehicle model identifier 179.

Next, FIG. 11B also depicts a display screen 101 displayed on thedisplay 43. The display screen 101 includes a main scanner menu 189. Theprocessor 40 can output the main scanner menu 189 in response to avariety of events, such as powering on the scanner 8 via the powerbutton 83 or a selection to return to the main scanner menu 189 whilethe display 43 is displaying a different display screen. The mainscanner menu 189, as well as the main scanner menu 109, can be displayedby the display 43 to provide a relatively simple display screen for avehicle body repair person.

As an example, the main scanner menu 189 includes the read DTC selector190 (shown as “DTC”) selectable to cause the processor 40 to transmit aVDM to request DTC from an ECU in the vehicle 1. The processor 40 cantransmit a VDM to request DTC from each ECU capable of setting DTCwithin the vehicle 1. The processor 40 can determine DTC set in thevehicle 1 from each VDM from the vehicle 1 reporting any DTC set in theECU that sent the VDM. After determining the DTC set in the vehicle 1,the processor 40 can cause the display 43 to display a list of the DTC,such as the list of DTC 133 (shown in FIG. 8B).

As still yet another example, the main scanner menu 189 includes aselector 191 (shown as “DAMAGE”) selectable to cause the scanner 8 totransition to an operating state in which the scanner 8 operates todetermine information regarding a damaged vehicle, such as a damagedportion at which the vehicle is damaged. The processor 40 can respond todetermining the selector 191 was selected in the same way in which theprocessor 40 responds to determining the selector 113 (shown in FIG. 6A)was selected.

As another example, the main scanner menu 189 includes a selector 192(shown as “ADJUSTMENTS”) selectable to cause the display 43 to display avehicle adjustment menu, such as the vehicle adjustment menu 240 shownin FIG. 13B.

Next, FIG. 12A also depicts a display screen 102 displayed on thedisplay 43. The display screen 102 includes DTC information 195pertaining to the DTC C0040 selected from the list of DTC 133. At leastsome of the DTC information 195 shown in the display screen isselectable. For example, a reset procedure selector 197 for a resetprocedure “R2” is selectable. In response to determining the resetprocedure selector 197 is selected, the processor 40 can cause thedisplay screen 103 shown in FIG. 12B to be displayed. Other informationselectors displayed as part of information pertaining to a DTC that areselectable can include one or more of the following: an initializationselector, a program selector, or a calibration selection. The displayscreen 102 includes an adjustment selection 196 selectable to cause theprocessor 40 to cause the display 43 to display the display screen 105(shown in FIG. 13B). The display screen 102 includes an order partselector 198 selectable to cause the processor 40 to cause the display43 to display the display screen 106 (shown in FIG. 14A). The displayscreen 102 includes an order tool selector 199 selectable to cause theprocessor 40 to cause the display 43 to display the display screen 107(shown in FIG. 14B).

Next, FIG. 12B also depicts a display screen 103 displayed on thedisplay 43. The display screen 103 includes information 230 pertainingto the reset “R2” selected from the DTC information 195 shown in FIG.12A. The display screen 103 includes a reset selector 231 selectable tocause the processor 40 and/or the VCT 42 to transmit one or more VDM tothe ECU 3 in the vehicle 1 to perform the reset “R2”. The display screen103 includes a report selector 232 selectable to cause the processor 40to transmit add to the collision report 68 data regarding performance ofthe reset “R2.” The data regarding performance of the reset “R2” can,for example, include data indicating the reset “R2” was performed to thevehicle 1, and an outcome of performing the reset “R2,” such as resetperformed successfully, reset preformed partially, reset performedunsuccessfully.

Next, FIG. 13A also depicts a display screen 104 displayed on thedisplay 43. The display screen 104 includes a damaged selection menu220. The processor 40 can output the damaged selection menu 220 inresponse to a variety of events, such as determining a selection from ascanner menu (e.g., the main scanner menu 109,189) has been selected,such as the selector 113 (shown in FIG. 6A) or the selector 191 (shownin FIG. 11B). As an example, the damage selection menu 220 includes aselector 221 selectable to cause the scanner 8 to display a vehicle gridfor selecting a damaged portion of a vehicle. As another example, thedamage selection menu 220 includes a selector 222 selectable to causethe scanner 8 to activate the capture device 45 for capturing an imagethat shows the damaged location of the vehicle. As yet another example,the damage selection menu 220 includes a selector 223 selectable tocause the scanner 8 to download an image showing a damaged portion of avehicle. The processor 40 can cause the network transceiver 41 torequest and/or receive the image showing the damaged portion from theserver 9 or an NCS, such as the NCS 24, 25, 26. As still yet anotherexample, the damage selection menu 220 includes a selector 224selectable to cause the scanner 8 to read a repair order regarding thevehicle to determine the damaged portion of a vehicle. The processor 40can cause the network transceiver 41 to request and/or receive therepair order from the server 9 or an NCS, such as the NCS 24, 25, 26. Asstill yet another example, the damage selection menu 220 includes aselector 225 selectable to cause the processor 40 to display a textfield for entering text describing a damaged portion of a vehicle viathe keypad 44.

Next, FIG. 13B also depicts a display screen 105 displayed on thedisplay 43. The display screen 105 includes a select vehicle adjustmentmenu 240. The vehicle adjustment menu 240 can include one or morevehicle adjustment selectors, such as a reset selector, aninitialization selector, a program selector, or a calibration selector.An adjustment selector can, but need not necessarily, pertain to the ECU3, a DTC, a component in the vehicle 1, or a system in the vehicle 1.The adjustment selectors in the vehicle adjustment menu 240 can beassociated with adjustments performable to vehicle components or vehiclesystems by the scanner 8. FIG. 13B shows the vehicle adjustment menu 240with adjustment selectors for resets “R1” and “R2,” initializations“I1,” I2,” and “I3,” programming “P1,” and calibrations “C1” and “C2.”

The processor 40 can cause the display 43 to display the vehicleadjustment menu 240 in response to determining the selector 192 (shownin FIG. 11B) was selected, determining the adjustment selection 196(shown in FIG. 12A) was selected, or in response to another selectionselected via the display 43 and/or the keypad 44. A selection from thevehicle adjustment menu 240 can be selected using the display 43 and/orthe cursor 89 and the keypad 44.

Selecting a selectable reset, initialization, program, or calibrationcan cause the processor to output a display screen associated with theselected reset, initialization, program, or calibration. As an example,the selectable reset “R2” 241 can be selected to cause the display todisplay the display screen 103 shown in FIG. 12B. Each of those displayscreens can include a selector selectable to cause the processor 40and/or the VCT 42 to transmit one or more VDM to the ECU 3 to performthe reset, initialization, program, or calibration.

Next, FIG. 14A also depicts a display screen 106 displayed on thedisplay 43. The display screen 106 includes an online part orderinginterface. The display screen 106 can be displayed in response toselecting a selector within another display screen shown on the display43, such as the order part selector 198 from the display screen 102(shown in FIG. 12A). The cursor 89 and keypad 44 and/or the display 43can be used to select any part to be ordered, a delivery option, and ashipping address if applicable.

Next, FIG. 14B also depicts a display screen 107 displayed on thedisplay 43. The display screen 107 includes an online tool orderinginterface. The display screen 107 can be displayed in response toselecting a selector within another display screen shown on the display43, such as the order tool selector 199 from the display screen 102(shown in FIG. 12A). The cursor 89 and keypad 44 and/or the display 43can be used to select any tool to be ordered, a delivery option, and ashipping address if applicable.

Next, FIG. 15A also depicts a display screen 180 displayed on thedisplay 43. The display screen 180 includes a vehicle image 260. Aportion of the vehicle image 260 can be selected in various ways toidentify a damaged portion of the vehicle. For example, the cursor 89could be used to select a portion of the vehicle image 260. As anotherexample, a user hand 261 can touch the display 43 to select a portion ofthe vehicle image 260. The next selector 147 shown on the display screen180 can be configured to indicate that selecting a damaged portion iscomplete. A touch screen input to the display 43 can rotate the vehicleimage 260 so that a portion of the vehicle not currently displayed canbe selected.

Next, FIG. 15B also depicts a display screen 181 displayed on thedisplay 43. The display screen 181 shows the vehicle image 260 afterselection of a portion 262 (e.g., the right rear quarter). The processor40 can cause the portion 262 to be highlighted in some fashion toidentify the portion has been selected. The next selector 147 shown onthe display screen 181 can be configured to indicate that selecting adamaged portion is complete.

Next, FIG. 15C also depicts a display screen 182 displayed on thedisplay 43. The display screen 182 shows selector boxes 700, 701, 702configured for entering selections of a vehicle year, make, and model,respectively. The processor 40, 440 can determine a vehicle model basedon the selections made via the selector boxes 700, 701, 702 and causethe display 43 to show the vehicle model on a display screen. Theprocessor 40 can select, from the image 65, an image 703 of a vehicleassociated with the entered year, make, and model. The processor 40 canoutput the image 703 on the display 43. The image 703 shows at least aportion of an undamaged vehicle. For purposes of this application, theimage 703 includes shade lines to distinguish the image 703 from animage that will be captured by the scanner 8. The display 43 and/or thekeypad 44 can be used to rotate the image 703 so that a differentportion of the vehicle (such as the left side of the vehicle) isdisplayed on the display 43. A user may rotate the image 703 for acircumstance in which a portion of a damaged vehicle to be compared tothe image 703 is not represented by the view of the image 703 currentlydisplayed by the display 43. As an example, a swirl input onto thedisplay 43 could be used to rotate the image 703. As another example, aswipe input onto the display 43 could be used to rotate the image 703.Other touch screen inputs, such as a pinching input or a spreadinginput, applied to the display 43 can cause the processor 40, 440 toresize an image 703, 705 to align with the other image.

Next, FIG. 15D also depicts a display screen 183 displayed on thedisplay 43. The display screen 183 shows the image 703 of the undamagedvehicle and the button label 704 associated with the button 85. Thebutton 85 or some other user interface component on the scanner 8 can beconfigured to capture an image, such as the image 705 of a damagedvehicle, while the image 703 is displayed on the display 43. Theprocessor 40, 440 can cause the image 703 or the image 705 to beoverlaid upon the other.

As shown in FIG. 15D, the image 703 displays the undamaged vehicle at ascale smaller than a scale at which the image 705 displays the damagedvehicle. A user interface component of the scanner 8 can be user tochange the scale of one or more of the image 703 or the image 705 sothat scale of the images 703, 705 is identical or at least substantiallyidentical. A user interface component of the scanner 8 can be used toalign one or more of the images 703, 705 so that one of the images 703,705 is overlaid upon the other. Additionally or alternatively, theprocessor 40, 440 can change the scale of the image 703 or the image 705to align the images 703, 705. The alignment can be based on aligningedges of the vehicle shown in the images, such as an edge representing aroofline of the vehicle shown in the images 703, 705.

Next, FIG. 15E depicts a display screen 184 displayed on the display 43after the images 703, 705 have been aligned. The image 705 of thedamaged vehicle can be overlaid upon the image 703. Alternatively, theimage 703 of the undamaged vehicle can be overlaid upon the image 705 ofthe damaged vehicle. Aligning the images 703, 705 can include capturingthe image 705 while a vehicle displayed on the display 43 is alignedwith the image 703. A user may adjust a zoom setting on the scanner 8 sothat the displayed image is at the same scale as the image 703 whencapturing the image 705. Additionally or alternatively, a user can movethe scanner 8 closer to or farther away from the damaged vehicle inorder to capture the image 705 with the same scale as the image 703.Furthermore, the processor 40, 440 can scale the images 703, 705. Forinstance, the processor 40 can be configured to increase or decrease asize of the image 703, 705 to change the scale of image 703, 705.Furthermore still, the processor 40, 440 can align the images 703, 705.For instance the processor 40, 440 can reposition an image 703, 705until edge lines of the vehicles shown in one of the images 703, 705 isoverlaid or under an edge line of a similar portion of the vehicle shownin the other image.

After alignment of the images 703, 705, the processor 40 cansubsequently determine a portion of the damaged vehicle shown in theimage 705 that is damaged. The processor 40 can compare edge lines ofthe vehicle shown in the images 703, 705 to determine edge lines that donot match. The edge lines of the image 705 that do not match the edgelines of the image 705 may be indicative of the damaged portion. Forexample, FIG. 15E shows an edge line 707 between arrows 708, 709 of theundamaged vehicle shown in the image 703 and an edge line 706 betweenthe arrows 708, 709 of the damaged vehicle shown in the image 705. Theprocessor 40, 440 can thus determine that the damaged portion of thedamaged vehicle is located at a portion of the vehicle represented bythe edge line 706 between the arrows 708, 709. As another example, theprocessor 40,440 can determine a gap between two body components (e.g.,a door and a fender) shown in the image of the damaged vehicle isgreater than a gap between the same two body components in the referenceimage of the vehicle.

Next, FIG. 15F depicts a variation of the scanner 8 that differs fromthe variation of the scanner 8 shown in FIG. 6A to FIG. 15E. In thisvariation, the scanner includes the display 43, but fewer hardware keysthan the variation of the scanner shown in FIG. 6A to FIG. 15E. Forinstance, the scanner 8 includes the direction keypad 80, the yes button81, the no button 82, and the power button 83 as hardware keys, but notthe buttons 85, 86, 87, 88 and the multi-button keypad 84. Similar tothe display 43 shown in FIG. 6A to FIG. 15E, the display 43 can includea touch screen display, such as a capacitive touch screen display. Inthe implementation shown in FIG. 15F, the display 43 is shown toindicate that some functions selectable by hardware buttons, such as thebuttons 85, 86, and 88, can be selected using a touch screen display.For instance, the display 43 is shown as displaying a display screen 185that includes the vehicle images 150, 151, 152 shown in FIG. 9A. For thescanner shown in FIG. 15F, the vehicle image 150, 151, 152 can beselected by touching a selector box 715, 716, 717, respectively, on thedisplay 43.

Next, FIG. 15G to FIG. 15N depict a variation of the scanner 8 thatdiffers from the variations of the scanner 8 shown in FIG. 6A to FIG.15F. In this variation, the scanner 8 includes the display 43 (e.g., atouch screen display), but does not include any hardware keys. In thisimplementation, a touch screen input to the display 43 can cause thescanner 8 to (1) change power states from a sleep mode to a power-onmode, (2) make a selection, such as any selection (described in thisdescription) as being made via the scanner 8, (3) change power statesfrom a power-on mode to a sleep mode, and/or (4) display any displayscreen shown in FIG. 6A to FIG. 15E. As an example, the scanner 8configured without any hardware keys can minimize battery usage by thescanner 8, such as by turning off a backlighting for the display 43,during the sleep mode. The scanner 8 that includes one or more hardwarekeys can also implements the power-on and sleep modes.

FIG. 15G also depicts the display 43 displaying a display screen 186including the vehicle model identifier 320, an identifier of POI damage321, a selector 322 configured for causing the processor 40, 440 toinclude content regarding the POI damage onto a collision report, and aselector 323 configured for causing the processor 40, 440 to determinePRCD based on the POI damage indicated by the identifier of the POIdamage 321 and/or based on the vehicle identified by the vehicle modelidentifier 320. The processor 40 can be configured to notify theprocessor 440 of the selector 322 being selected so that the processor440 includes content regarding the POI damage onto a collision report.The processor 40 can be configured to notify the processor 440 of theselector 323 being selected so that the processor 440 determines RCDbased on the POI damage indicated by the identifier of the POI damage321 and/or based on the vehicle identified by the vehicle modelidentifier 320. The processor 40, 440 can determine the vehicle modelidentifier 320 as described elsewhere in this description.

Next, FIG. 15H depicts the display 43 displaying a display screen 187that can, but need not necessarily, be shown in response to selection ofthe selector 323 and then the next selector 147 while the display screen186 (shown in FIG. 15G) is displayed. The display screen 187 shows thevehicle model identifier 320, and PRCD data 805, 806, 808, 809. The PRCDdata 805, 806 can be applicable multiple vehicle models (as shown inFIG. 16B). The PRCD data 808, 809 can be applicable to a single vehiclemodel (i.e., the vehicle model VM1). Other vehicle models may likewisebe associated with RCD that matches the PRCD data 808 or 809.Furthermore, the display screen 187 includes a selector 328 to view acollision report, and selectors 329, 331, 333, 335 selectable toindicate an inspection hint regarding the PRCD data 805, 806, 808, 809,respectively, is selected. Furthermore still, the display screen 187 caninclude selectors 330, 332, 334, 336 selectable to indicate the PRCDdata 805, 806, 808, 809, respectively, is selected for adding to acollision report. Moreover, a selector within the selectors 330, 332,334, 336 can include a quantity selector to indicate a quantity of RCDto be added to the collision report and a location for each RCD. Asshown in FIG. 15H, quantities and locations of three different seatbelts and seat belt retractor pre-tensioners have been entered for theselectors 330, 332, respectively.

Next, FIG. 15I depicts the display 43 displaying a display screen 853that can, but need not necessarily, be shown in response to selection ofthe selector 323 and then the next selector 147 while the display screen186 (shown in FIG. 15G) is displayed. The display screen 853 shows aPRCD identifier 861 (i.e., Excessive driver door gap), an inspectionhint 862 (i.e., a standard gap adjacent the right-side driver door is3/16″), and measurement fields 857, 858, 859, 860 in which a measurementof a gap between the right side door and an adjacent vehicle componentin proximity to the lines leading from the measurement fields 857, 858,859, 860. As shown in FIG. 15I, a measurement field 860 can include amenu from which a measurement can be selected using a touch screen ofthe display 43 or the keypad 44. Other measurement fields on displayedon the display can include appropriate menus for selecting ameasurement.

Next, FIG. 15J depicts the display 43 displaying a display screen 188that can, but need not necessarily, be shown in response to selection ofthe selector 335 while the display screen 187 (shown in FIG. 15H) isdisplayed. The display screen 188 shows an inspection hint regarding aseat belt retractor pre-tensioner. The next selector 147, back selector149 can be selected to cause the processor 40, 440 to output a differentdisplay screen. As an example, selection of the next selector 147 whilethe display screen 188 is shown could cause another inspection hintregarding the seat belt retractor pre-tensioner. As another example,selection of the back selector 149 while the display screen 188 is showncould cause the display 43 to show the display screen 187 shown in FIG.15H.

Next, FIG. 15K depicts the display 43 displaying a display screen 850that can, but need not necessarily, be shown in response to selection ofthe back selector 149 while the display screen 188 (shown in FIG. 15J)is displayed. The display screen 850 shown in FIG. 15K is the same asthe display screen shown in FIG. 15H except that a quantity and locationhave been entered into the selector 336 and the view collision reportselector 328 has been selected. Selecting the next selector 147 whilethe display screen 850 shown in FIG. 15K is shown can cause theprocessor 40, 440 to display a collision report on the display 43.

Next, FIG. 15L depicts the display 43 displaying a display screen 851that can, but need not necessarily, be shown in response to theprocessor 40, 440 determining POI damage for a vehicle identified as thevehicle model VM1. The display screen 851 includes the vehicle modelidentifier 320, the identifier of the POI damage 321, the selector 323(discussed with respect to FIG. 15G), a selector 324 selectable to causethe processor 40, 440 to determine a technical service bulletin relatedto the determined POI damage and/or the PRCD, and a selector 325selectable to cause the processor 40, 440 to determine a positionstatement by an OEM (e.g., a vehicle OEM or a vehicle component OEM)related to the determined POI damage and/or the PRCD. The processor 40,440 can determine the related bulletins and/or position statements fromthe TSB and position statement 70, 470.

Next, FIG. 15M depicts the display 43 displaying a display screen 852that can, but need not necessarily, be shown in response to selection ofthe next selector 147 while the display screen 851 (shown in FIG. 15L)is displayed. The display screen 852 includes the vehicle modelidentifier 320, a TSB 855, and a position statement 856. The TSB 855 andthe position statement 856 can be stored within the TSB and positionstatement 70, 470.

Next, FIG. 15N depicts the display 43 displaying a display screen 854that can, but need not necessarily, be shown in response to selection ofthe squib status selector 114 while the display screen 90 (shown in FIG.6A) is displayed. The display screen 854 includes the squib statusinformation 863 determined by the processor 40. As shown in the displayscreen 854, the squib status for the vehicle identified by the vehiclemodel identifier 320 is “used” for both driver side air bag squibs andsquib #1 associated with a front passenger side air bag, and “live” forsquib #2 associated with the front passenger side air bag. The displayscreen 854 also includes an instruction selector 865 to cause theprocessor 40 to output instructions for handing an air bag with a livesquib.

Next, FIG. 15O depicts the display 43 displaying a display screen 870that can, but need not necessarily, be shown in response to selection ofthe read DTC selector 110, 190. The display screen 870 includes thevehicle grid 134 and a grid legend 871. The vehicle grid 134 includes animage of a vehicle. The processor 40 can obtain the image shown in thevehicle grid 134 from the image 65. The grid legend 871 includes anindicator 874 that pertains to highlighting 872 within vehicle gridlocation 139R. The grid legend 871 includes an indicator 875 thatpertains to highlighting 873 within vehicle grid location 136C. Thehighlighting 872, 873 provides an indication of where vehiclecomponent(s) associated with the DTC C1165 and the DTC P0118,respectively, are located on the vehicle 1. Selection of a vehicle gridlocation of a vehicle grid can cause the processor 40 to output avehicle grid showing another image of a portion of the vehicle 1represented by the portion of the image shown in the selected vehiclegrid location. The other image can show details not shown in the imagewithin the selected vehicle grid location. As an example, the otherimage may show details behind a vehicle body panel, such as a vehiclehood covering an engine compartment.

Next, FIG. 15P depicts the display 43 displaying a display screen 880that can, but need not necessarily, be shown in response to selection ofthe vehicle grid location 136C while the display 43 is displaying thedisplay screen 870. The display screen 880 includes a vehicle grid 881with vehicle grid columns 882, 883, 884, 885, 886, each of whichcorresponds to a right, center, and left grid position. The vehicle grid881 includes an image of an engine compartment of the vehicle 1. Theprocessor 40 can obtain the image shown in the vehicle grid 881 from theimage 65 as the memory 47 can store data that indicates the image shownin the vehicle grid 881 is associated with a portion of the vehicle 1represented by the portion of the image shown in the selected vehiclegrid location 136C. Referring to Table 2, the image displayed on thedisplay screen 880 is an image named VM1_136C.jpg. The display screen880 includes a grid legend 887 having an indicator 888 that pertains tohighlighting 889 within the center position of vehicle grid column 883.The highlighting 889 provides an indication of where vehiclecomponent(s) associated with the DTC P0118 are located on the vehicle 1.

TABLE 4 Vehicle Grid Vehicle Location Component DTC Symptom 882RRadiator Null Leaking coolant, engine overheating 882C Radiator, NullLeaking coolant, engine cooling fan overheating 882L Radiator NullLeaking coolant, engine overheating 883R Fuel injector #2, P0202 Enginemisfire—cylinder spark plug #2 #2 883C Engine coolant P0118 Leakingcoolant, engine temperature overheating sensor, water pump 883L Fuelinjector #1, P0201 Engine misfire—cylinder spark plug #2 #1 884R Fuelinjector #4, P0204 Engine misfire—cylinder spark plug #4 #4 884C Intakemanifold Null 884L Fuel injector #3, P0203 Engine misfire—cylinder sparkplug #3 #3 885R Fuel injector #6, P0206 Engine misfire—cylinder sparkplug #6 #6 885C Intake manifold Null 885L Fuel injector #5, P0205 Enginemisfire—cylinder spark plug #5, #5, engine does not start electricstarter 886R Null Null Null 886C Flywheel, coil pack 886L Null Null Null

Next, FIG. 15Q illustrates some example inputs (i.e., touch screeninputs) 690, 691, 692, 693, 694, 695 that can be entered onto a touchscreen display. The processor 40 can detect a touch screen input andperform a function associated with the touch screen input. The functioncan further be associated with the content currently displayed on thedisplay 43 while the touch screen input is occurring. The example touchscreen inputs are shown with one or two dashed circle(s) to represent astarting point of one or two digit(s) (e.g., finger and/or thumb). Thearrows between the circles represent example directions of movement. Thedirections of movement for touch screen inputs 690, 691, 692, 695 canoccur in an opposite direction. The touch screen input 690 is ahorizontal swipe input (when the display 43 is in a portrait orlandscape orientation). The touch screen input 691 is a vertical swipeinput (when the display 43 is in a portrait or landscape orientation).The touch screen input 692 is a diagonal swipe input (when the display43 is in a portrait or landscape orientation). The touch screen input693 is a pinch input. The touch screen input 694 is an expand input. Thetouch screen input 691 is a swirl input. The touch screen inputs 693,694 are shown as vertical inputs, but can alternatively be enteredhorizontally and/or diagonally. Other examples of touch screen inputsare available.

VII. Additional Example Operation

Next, FIG. 18A shows a flowchart depicting a set of functions 725 (ormore simply “the set 725”) that can be carried out in accordance withthe example implementations described in this description. The set 725includes the functions shown in blocks labeled with whole numbers 726through 730. The description of the set 725 includes references toelements shown in other figures described in this description, but thefunctions of the set 725 are not limited to being carried out only bythe referenced elements. A variety of methods can be performed using allof the functions shown in the set 725 or any proper subset of thefunctions shown in the set 725. Any of those methods can be performedwith other functions such as one or more of the other functionsdescribed in this description. A processor can perform or cause afunction of the set 725 to be performed.

In some example implementations, the scanner 8 can perform one or moreof the functions of the set 725, and one or more of those functionsperformed by the scanner 8 can be performed by the processor 40. In atleast some of those implementations, the scanner 8 can perform all ofthe functions of the set 725. The scanner 8 and the processor 40 canperform functions of the set 725 while the scanner 8 is operativelyconnected to the vehicle 1 via the VCL 10.

In some other example implementations, the server 9 can perform one ormore of the functions of the set 725, and the one or more of thosefunctions performed by the server 9 can be performed by the processor440. In at least some of those implementations, the server 9 can performall of the functions of the set 725. The server 9 and the processor 440can perform functions of the set 725 while the server 9 is operativelyconnected to the scanner 8 via the network 11 or to a vehicle, such asthe vehicle 1. Furthermore, in some other example implementations, thescanner 8 and the server 9 can both perform one or more of the functionsof the set 725. In those example implementations, the server 9 canprovide the scanner 8 with a display screen to shown on the display 43.

Block 726 includes determining a vehicle model associated with a firstvehicle. The processor 40, 440 can determine the vehicle model asdescribed elsewhere in this description. The description of block 501,shown in FIG. 5A, describes examples of determining the vehicle model.For implementations in which the server 9 determines the vehicle model,the server 9 can determine the vehicle model based on a communicationsent to the server 9 from the scanner 8. That communication can includean identifier of the vehicle.

Next, block 727 includes determining POI damage to the first vehicle.The processor 40, 440 can determine the POI damage as describedelsewhere in this description. The description of FIG. 9A, FIG. 9B, FIG.10A, FIG. 13A, and FIG. 15A to FIG. 15F describes examples ofdetermining a point-of-impact to a vehicle, which can be a POI where thePOI damage occurred. A vehicle can include more than onepoint-of-impact, such as a vehicle that was involved in a firstcollision where the vehicle collided with another vehicle in front ofthe vehicle and a second collision where another vehicle collided withthe rear of the vehicle.

Next, block 728 includes determining PRCD to the first vehicle. Theprocessor 40, 440 can determine the PRCD as described elsewhere in thisdescription. The description of FIG. 15G to FIG. 15N describes someexamples of determining PRCD. In some implementations, the processor 440determines the PRCD and transmits the PRCD to the scanner 8. A benefitof determining PRCD can include expediting repair of a damaged vehicle.

Furthermore, in some implementations, determining the PRCD can includedetermining a DTC set in the first vehicle is collision-related. As anexample, the processor 40, 440 can make that determination as describedin this elsewhere in this description. In these implementations,determining the PRCD can also include determining a component related(i.e., a ‘related component’) to the collision-related DTC. As anexample, the processor 40, 440 can refer to the VRD 66, 300, 466 todetermine a related component based on the collision-related DTC.

In some implementations, determining the PRCD can include determiningthe PRCD is related to the POI damage to the first vehicle. As anexample, the processor 40, 440 can refer to the VRD 800 to determinethat the PRCD data 805, 806 is applicable to vehicles (from amongmultiple vehicle models including the vehicle model of the firstvehicle) having POI damage data 804 matching the POI damage theprocessor 40, 440 determined occurred to the first vehicle. As anotherexample, the processor 40, 440 can refer to the VRD 802 to determinethat the PRCD data 808, 809 is applicable to all vehicles that are thevehicle model VM1 having POI damage data 807 matching the POI damage theprocessor 40, 440 determined occurred to the first vehicle.

Next, block 729 includes showing an identifier of the RCD to the firstvehicle. As an example, the display 43 can display a display screen,such as the display screen 187 (shown in FIG. 15H), the display screen850 (shown in FIG. 15K) or the display screen 852 (shown in FIG. 15M).As another example, the display 43 can show the collision report 68 thatincludes an identifier of the RCD to the first vehicle. As shown in FIG.17, the collision report 68 shows identifiers of the RCD in the repairparts section including the seat belts and seat belt retractorpre-tensioner.

Next, block 730 includes augmenting a collision report based on thedetermined PRCD to the first vehicle. As an example, augmenting thecollision report 68 can include adding identifiers of the RCD, such asthe identifiers of the RCD in the repair parts section including theseat belts and seat belt retractor pre-tensioner. As another example,augmenting the collision report 68 can include adding a quantity ofparts, a unit cost per part, and a total cost of parts arising from theRCD. In some implementations, augmenting the collision report withidentifiers of the RCD can be conditioned on the scanner 8 receiving aninput indicative that PRCD actually occurred to the vehicle.

Next, FIG. 18B and FIG. 18C depict display screen 735, 736,respectively, displayed on the display 43. The display screen 735 showsthe vehicle grid 148 in which a damage area 737 (represented by diagonallines) has been selected within the grid locations 146LR, 146MR, 145LR,145MR. Likewise, the display screen 736 shows the vehicle grid 134 inwhich a damage area 738 (represented by diagonal lines) has beenselected within the grid locations 135R, 136R. The damage area 738 canbe used to determine an amount of deflection of vehicle components ofthe damaged vehicle.

The scanner 8 can be arranged in one or more configuration to allow auser to make selections to identify the damage areas 737, 738. In atleast some implementations, a scale of the grid locations are finer thanthe grid locations shown in FIG. 18B, 18C (e.g., grid locations coveringa smaller portion of a vehicle and/or more grid locations covering thevehicle). In those implementations, as well as any other implementationusing a vehicle grid with multiple grid locations, a grid location canhave a non-rectangular shape. The processor 40 can detect which gridlocations have been selected in the vehicle grid 148 to determine thedamage area 737. Likewise, the processor 40 can detect which gridlocations have been selected in the vehicle grid 134 to determine thedamage area 738.

In at least some implementations, a portion of a vehicle displayed onthe display 43 can be selected by tracing an outline of the portion onthe display. As an example, the tracing can occur by a user touching thetouch screen. As another example, the tracing can occur by moving thecursor 89 on the display 43. A perimeter of an area formed by moving thecursor 89 can indicate the damage area 737, 738.

In at least implementations, the display 43 can include a paint selector739 for use in selecting portions of a vehicle displayed on the display43 or other portions of an item displayed on the display 43. The display43 can also include an eraser selector 740 for use in deselecting aportion of the displayed vehicle or other displayed item selected by useof the paint selector 739. Once the paint selector 739 is active thecursor 89 or a digit of the user, for example, can be used to select theportion. The processor 40 can show the selected area with arepresentation as having been painted.

The processor 40 can quantify an amount of deflection reflected in eachgrid location or an amount of deflection reflected in a portion of thevehicle shown in each grid location. In some implementations, theprocessor 40 can determine the vehicle deflection represented in gridlocation 135R is 75% and the vehicle deflection represented in the grid136R is 30%. In other words, 75% of the vehicle shown in grid location135R is indicated to be damaged and/or 25% of the vehicle shown in gridlocation 135R is shown as undamaged (i.e., not damaged), and 30% of thevehicle shown in grid location 136R is indicated to be damaged and/or70% of the vehicle shown in grid location 136R is shown as undamaged. Inother implementations, the processor 40 can determine the vehicle damagerepresented in grid locations 135R, 136R in terms of area or distance.

The processor 40, 440 can refer to the CADD 69, 467 to determinevehicles of the same vehicle model that experienced a similar amount ofvehicle deflection in the same portions of the vehicle identified by thescanner 8. The processor 40, 440 can determine repairs made to thedetermined vehicles and display the repairs on a display screen as PRCD.As an example, the similar amount of vehicle deflection can be an amountof vehicle deflection within a range of the determined vehicledeflection plus or minus a threshold amount of vehicle deflection. Thethreshold amount of vehicle deflection can, but need not necessarily, befive percent, ten percent, of fifteen percent.

In one implementation, the processor 40 can determine the amount ofdeflection within a vehicle grid or a portion of a vehicle grid based onpixel quantities. For instance, the portion of the vehicle shown in thegrid location 135R can cover 2,000 pixels and the amount of deflectionrepresented in the grid location 135R can cover 1,500 pixels, such thatthe processor 40 can determine the amount of deflection by dividing the1,500 pixels by 2,000 pixels to obtain the 75% deflection value.

Tables 5, 6, and 7 show examples of deflection data and repair data forother vehicles that are the same vehicle year, make, and model as thecurrent vehicle identified by the scanner 8. Tables 5, 6, and 7 show thegrid locations of the vehicle grid 134 (shown in FIG. 9B) and amounts ofdeflection determined for the portions of a vehicle shown in each gridposition. Additionally, Tables 5 and 6 show repairs made to theparticular vehicles identified in those tables and a cost associatedwith each of those repairs. Table 7 shows that no repairs were made tothe particular vehicle identified in that table. The vehicle identifiedin Table 7 was “totaled” because the costs to repair the vehicle due tothe amount of vehicle damage were considered to be too great. As anexample, Repair R1 is replacement of the right front fender, Repair R2is replacement of the B-pillar, Repair R3 is replacement of the frontrow right seat belt retractor pre-tensioner, Repair R4 is replacement ofright front wheel speed sensor, Repair R5 is replacement of radiator,Repair R6 is replacement of front grill, Repair R7 is replacement ofvehicle headlights, Repair R8 is replacement air conditioner condenser,and Repair R9 is replacement of vehicle hood. The repairs shown inTables 5 and 6 can be considered PRCD for other vehicles thatexperienced vehicle deflection similar to the deflection values shown inthose tables.

TABLE 5 Null 135 136 137 138 139 140 R 68% 22% 0% 0% 0% 0% C  5%  0% 0%0% 0% 0% L  0%  0% 0% 0% 0% 0% (Repair R1, Cost C1), (Repair R2, CostC2), (Repair R3, Cost C3), (Repair R4, Cost C4) Vehicle: 2017 BetaTango-VIN 2G1FP22K67406002

TABLE 6 Null 135 136 137 138 139 140 R 53% 8% 0% 0% 0% 0% C 15% 0% 0% 0%0% 0% L 32% 0% 0% 0% 0% 0% (Repair R1, Cost C1), (Repair R2, Cost C2),(Repair R3, Cost C3), (Repair R4, Cost C4), (Repair R5, Cost C5),(Repair R6, Cost C6), (Repair R7, Cost C7), (Repair R8, Cost C8),(Repair R9, Cost C9) Vehicle: 2017 Beta Tango-VIN 2G1FP22K67231223

TABLE 7 Null 135 136 137 138 139 140 R 100% 100% 0% 0% 0% 0% C 100% 100%0% 0% 0% 0% L 100% 100% 0% 0% 0% 0% Repairs: None-vehicle totaledVehicle: 2017 Beta Tango-VIN 2G1FP22K674712626

The processor can compare deflection data and repair data regardingdifferent vehicles of a common vehicle model to determine a thresholdthat indicates a DTC is collision-related. For example, when theprocessor determines a particular portion of a vehicle that includes awire harness experiences deflection of at least 50%, the wire harness istypically damaged, and the damaged wire harness results in a particularDTC being set active. In accordance with that example, the processor candetermine a DTC set in vehicle 1 is collision-related by determining theparticular portion of vehicle 1 has experienced at least 50% deflection.Moreover, the processor may associate a confidence rating with respectto the determination the DTC is collision-related. The processor candetermine the confidence rating based on the amount of deflection. Insome cases, the greater amount of deflection at the particular portionof the vehicle, the greater the confidence rating, and vice versa.

VIII. Example Computing System Configuration

Next, FIG. 19 is a simple block diagram of a computing system 650 inaccordance with the example implementations. In a basic configuration651, the computing system 650 can include one or more processors 652 anda system memory 654. A memory bus 659 can be used for communicatingbetween the processor 652 and the system memory 654. Depending on thedesired configuration, the processor 652 can be of any type includingbut not limited to a microprocessor (μP), a microcontroller (μC), adigital signal processor (DSP), or any combination thereof. A memorycontroller 653 can also be used with the processor 652, or in someimplementations, the memory controller 653 can be an internal part ofthe processor 652.

Depending on the desired configuration, the system memory 654 can be ofany type including but not limited to volatile memory (such as RAM),non-volatile memory (such as ROM, flash memory, etc.) or any combinationthereof. The system memory 654 can include one or more applications 655,and program data 657. The application 655 can include an algorithm 656that is arranged to perform the functions described as being performedby the scanner 8, or the server 9, or the NCS 24, 25, 26. The programdata 657 can include system data 658 that could be directed to anynumber of types of data, such as one more of the following types ofdata: a vehicle model identifier 61, a DTC data 62, a vehicle portionidentifier 63, captured data 64, an image 65, VRD 66, CADD 69, a displayscreen 67, and a collision report 68. In some example implementations,the applications 655 can be arranged to operate with the program data657 on an operating system executable by the processor 652.

The computing system 650 can have additional features or functionality,and additional interfaces to facilitate communications between the basicconfiguration 651 and any devices and interfaces. For example, storagedevices 660 can be provided including removable storage devices 661,non-removable storage devices 662, or a combination thereof. Examples ofremovable storage and non-removable storage devices include magneticdisk devices such as flexible disk drives and hard-disk drives (HDD),optical disk drives such as compact disc (CD) drives or digitalversatile disk (DVD) drives, solid state drives (SSD), and tape drivesto name a few. Computer storage media can include volatile andnonvolatile, non-transitory, removable and non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable program instructions, data structures, programmodules, or other data such as the data stored in a computer-readablememory, such at the memory 47.

The system memory 654 and the storage devices 660 are examples ofcomputer-readable medium, such as the memory 47. The system memory 654and the storage devices 660 can include, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by the computing system 650.

The computing system 650 can include or be implemented as a portion of asmall-form factor portable (i.e., mobile) electronic device such as asmartphone (e.g., an IPHONE® smartphone from Apple Inc. Of Cupertino,Calif., or a GALAXY S® smartphone from Samsung Electronics Co., Ltd. OfMaetan-Dong, Yeongtong-Gu Suwon-Si, Gyeonggi-Do, Republic of Korea), atablet device (e.g., an IPAD® tablet device from Apple Inc., or aSAMSUNG GALAXY TAB tablet device from Samsung Electronics Co., Ltd.), ora wearable computing device (e.g., a wireless web-watch device or apersonal headset device). The application 655, or the program data 657can include an application downloaded to the communication interfaces667 from the APP STORE® online retail store, from the GOOGLE PLAY®online retail store, or another source of the applications or the CRPI60. A component of the scanner 8, such as the display 43 and/or thenetwork transceiver 41, can be embodied in the small-form factorelectronic device.

The computing system 650 can include or be implemented as part of apersonal computing system (including both laptop computer and non-laptopcomputer configurations), or a server. The computing system 650 can beconfigured as an embedded system in which the processor 652 includes anembedded processor and the system memory 654 includes an embeddedmemory.

The computing system 650 can also include output interfaces 663 that caninclude a graphics processing unit 664, which can be configured tocommunicate to various external devices such as display devices 666 orspeakers via one or more A/V ports 665 or a communication interface 667.The communication interface 667 can include a network controller 668,which can be arranged to facilitate communications with the othercomputing systems 670 over a network communication via one or morecommunication ports 669. The communication connection is one example ofa communication media. Communication media can be embodied bycomputer-readable program instructions, data structures, programmodules, or other data in a modulated data signal, such as a carrierwave or other transport mechanism, and includes any information deliverymedia. A modulated data signal can be a signal that has one or more ofits characteristics set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media can include wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, radiofrequency (RF), infrared (IR) and other wireless media.

For the scanner 8, the communication interface 667 can include thenetwork transceiver 41 and the VCT 42, and the communication port 669can include a communication port connectable to a printer for printing apaper copy of the collision report 68.

Next, FIG. 20 is a schematic illustrating a conceptual partial view ofan example computer program product 680 that includes a computer programfor executing a computer process on a computing system, arrangedaccording to at least some implementations presented herein. Thatcomputer program can be encoded on a non-transitory computer-readablestorage medium in a machine-readable format, or on anothernon-transitory medium or article of manufacture.

In one implementation, the example computer program product 680 isprovided using a signal bearing medium 681. The signal bearing medium681 can include one or more programming instructions 682 that, whenexecuted by one or more processors can provide functionality or portionsof the functionality described above with respect to FIG. 1 to FIG. 17.In some examples, the signal bearing medium 681 can encompass acomputer-readable medium 683, such as, but not limited to, a hard diskdrive, a Compact Disc (CD), a Digital Video Disk (DVD), a digital tape,or any other memory described herein. In some implementations, thesignal bearing medium 681 can encompass a computer recordable medium684, such as, but not limited to, memory, read/write (R/W) CDs, R/WDVDs, etc. In some implementations, the signal bearing medium 681 canencompass a communications medium 685, such as, but not limited to, adigital and/or an analog communication medium (e.g., a fiber opticcable, a waveguide, a wired communications link, a wirelesscommunication link, etc.). Thus, for example, the signal bearing medium681 can be conveyed by a wireless form of the communications medium 685(e.g., a wireless communications medium conforming to the IEEE 802.11standard or another transmission protocol).

The one or more programming instructions 682 can be, for example,computer executable and/or logic implemented instructions. In someexamples, a computing system such as the computing system 650 of FIG. 19can be configured to provide various operations, functions, or actionsin response to the programming instructions 682 conveyed to thecomputing system 650 by one or more of the following; thecomputer-readable medium 683, the computer recordable medium 684, or thecommunications medium 685.

The scanner 8 can include any of the components of the computing system650. The processor 40 can be configured like the processor 652. Thememory 47 can be configured as part of or all of the system memory 654or the storage devices 660. The network transceiver 41 can be configuredas part of or all of the communication interfaces 667.

In at least some implementations, the scanner 8, the server 9, the NCS24, 25, 26, and/or the computing system 650 includes a power source. Thepower source can include a connection to an external power source andcircuitry to allow current to flow to other elements connected to thepower source. As an example, the external power source can include awall outlet at which a connection to an alternating current can be made.As another example, the external power source can include an energystorage device (e.g., a battery) or an electric generator.

Additionally or alternatively, a power source can include a connectionto an internal power source and power transfer circuitry to allowcurrent to flow to other elements connected to the power source. As anexample, the internal power source can include an energy storage device,such as a battery. Furthermore, any power source described herein caninclude various circuit protectors and signal conditioners. The powersources described herein can provide a way to transfer electricalcurrents to other elements that operate electrically.

IX. Definitions

The term “data” within this description can be used interchangeably withthe term “information” or similar terms, such as “content.” The datadescribed herein can be transmitted and received via a communication. Asan example, any transmission of data or a communication described hereincan occur directly from a transmitting device (e.g., a transmitter) to areceiving device (e.g., a receiver). As another example, anytransmission of data or a communication described herein can occurindirectly from the transmitter to a receiver via one or moreintermediary network devices, such as an access point, an antenna, abase station, a hub, a modem, a relay, a router, a switch, or some othernetwork device. The transmission of any of data or a communicationdescribed herein can include transmitting the data or communication overan air interface (e.g., using radio signals (i.e., wirelessly)). Thetransmission of any of data or communication described herein caninclude transmitting the data or communication over a wire (e.g., asingle wire, a twisted pair of wires, a fiber optic cable, a coaxialcable, a wiring harness, a power line, a printed circuit, a CAT5 cable,or CAT6 cable). The wire can be referred to as a “conductor” or byanother term. As an example, transmission of data or a communicationover the conductor can occur electrically or optically.

A “collision estimate” is an estimate indicative to repairing a vehicleas a result of the vehicle being involved in a collision. A collisionestimate can include data indicative of labor fees, vehicle componentfees, hazardous material fees, subletting fees, and miscellaneous feesfor vehicle fluids, welding rods, storage fees, etc. A “collisionprocedure” is content indicative of one or more procedural steps orprocedures performable to repair a vehicle as result of the vehiclebeing involved in a collision. The content of a collision procedure can,for example, include textual content, an image, or a video. A collisionestimate and/or a collision procedure can be configured according to anindustry standard, such as a standard defined by CIECA.

A “DTC” is a diagnostic trouble code. A DTC can be manufacturer specificor industry specific, such as a DTC defined by the SAE® J2012 standardfor Diagnostic Trouble Code Definitions, dated December 2016, or a DTCdefined by the ISO® 15031-6 standard for diagnostic trouble codedefinitions, dated August 2015. A DTC can include a sub-code. Forinstance, a DTC can indicate that a sensor is out-of-range. A sub-codecan indicate why the sensor is out-of-range, such as a sub-codeindicating the sensor is shorted to ground, a sub-code indicating thesensor is open-circuited, or a sub-code indicating the sensor is shortedto voltage. Unless explicitly stated otherwise, any discussion in thisdescription of a DTC can include a DTC that includes or does not includea sub-code.

In this description, the articles “a,” “an,” and “the” are used tointroduce elements or functions of the example implementations. Theintent of using those articles is that there is one or more of theintroduced elements or functions. The word “next” is used to transitionfrom paragraphs or aspects described in the description and is notintended to indicate an order of occurrence of any functions of method.

In this description, the intent of using the term “and/or” within a listof at least two elements or functions and the intent of using the terms“at least one of,” “at least one of the following,” “one or more of,” or“one or more of the following” immediately preceding a list of at leasttwo components or functions is to cover each implementation including alisted component or function independently and each implementationincluding a combination of the listed components or functions. Forexample, an implementation described as including A, B, and/or C, or atleast one of A, B, or C, or at least one of the following: A, B or C, orone or more of A, B, or C, or one or more of the following: A, B, or Cis intended to cover each of the following possible implementations: (i)an implementation including A, but not B and not C, (ii) animplementation including B, but not A and not C, (iii) an implementationincluding C, but not A and not B, (iv) an implementation including A andB, but not C, (v) an implementation including A and C, but not B, (v) animplementation including B and C, but not A, and (vi) an implementationincluding A, B, and C. For the implementations including component orfunction A, the implementations can include one A or multiple A. For theimplementations including component or function B, the implementationscan include one B or multiple B. For the implementations includingcomponent or function C, the implementations can include one C ormultiple C. The use of ordinal numbers such as “first,” “second,”“third” and so on is to distinguish respective elements rather than todenote a particular order of those elements unless the context of usingthose terms explicitly indicates otherwise. The use of the symbol “$” asprefix to a number indicates the number is a hexadecimal number. The useof “at least one” is to indicate “one or more.”

Example location abbreviations shown in the figures and/or in thedescription include “LF” for left front, “RF” for right front, “LFU” forleft front upper and/or upper left front, “RFU” for right front upperand/or upper right front, “LRQ” for left rear quarter, “RRQ” for rightrear quarter, “LR” for left rear, “RR” for right rear, “RFQ” for rightfront quarter, “RT FRT” for right front, and “LT rear” for left rear,“CHMSL” for center high mounted stop lamp, and “inop” for inoperative.

X. Conclusions and Enumerated Example Embodiments

It should be understood that the arrangements described herein and/orshown in the drawings are for purposes of example only. As such, thoseskilled in the art will appreciate that other arrangements and elements(e.g., machines, interfaces, functions, orders, and/or groupings offunctions) can be used instead, and some elements can be omittedaltogether according to the desired results. Furthermore, variousfunctions described and/or shown in the drawings as being performed byone or more elements can be carried out by a processor executing CRPI orby a combination of hardware, firmware, and/or software. For purposes ofthis description, execution of CRPI contained in a memory to performsome function can include executing all of the program instructions ofthose CRPI or only a portion of those CRPI.

While various aspects and implementations are described herein, otheraspects and implementations will be apparent to those skilled in theart. The various aspects and implementations disclosed herein are forpurposes of illustration and are not intended to be limiting, with thetrue scope being indicated by the claims, along with the full scope ofequivalents to which such claims are entitled. It is also to beunderstood that the terminology used herein for the purpose ofdescribing particular implementations only, and is not intended to belimiting.

Embodiments of the present disclosure may thus relate to one of theenumerated example implementation (EEEs) listed below.

EEE 1 is a method comprising: determining, by one or more processors, avehicle model associated with a first vehicle; determining, by the oneor more processors, a first diagnostic trouble code (DTC) set within afirst electronic control unit (ECU) in the first vehicle; determining,by the one or more processors, a first damaged portion of the firstvehicle, wherein the first damaged portion indicates where the firstvehicle was damaged by a collision; determining, by the one or moreprocessors, the first DTC is collision-related, wherein determining thefirst DTC is collision-related includes determining, by the one or moreprocessors, the first damaged portion of the first vehicle matches areference vehicle portion associated with both a component attributableto setting the first DTC and the vehicle model associated with the firstvehicle; and outputting, by the one or more processors, a collisionreport that indicates the first DTC is collision-related.

EEE 2 is the method of EEE 1, wherein outputting the collision reportincludes displaying the collision report on a display, and wherein thecollision report includes a vehicle adjustment selector applicable tothe first vehicle, the method further comprising: receiving, by the oneor more processors, a selection of the vehicle adjustment selector; andadjusting the vehicle in response to receiving the selection of thevehicle adjustment selector.

EEE 3 is the method of EEE 2, wherein adjusting the vehicle includescalibrating a component on the first vehicle, programming the componenton the first vehicle, resetting a component on the first vehicle, orinitializing a component on the first vehicle.

EEE 4 is the method of any one of EEEs 1 to 3, further comprising:outputting, by the one or more processors to a display, an imageassociated with the vehicle model, wherein the image is divided intomultiple selectable image portions, wherein a first selectable imageportion of the multiple selectable image portions corresponds to a firstportion of the vehicle model, and wherein determining the first damagedportion of the first vehicle includes receiving, by the one or moreprocessors, a selection of the first selectable image portion thatcorresponds to the first portion of the vehicle model.

EEE 5 is the method of EEE 4, wherein receiving the selection of thefirst selectable image portion includes the one or more processorsdetermining a portion of the display at which the first selectable imageportion is displayed is touched.

EEE 6 is the method of EEE 4, wherein receiving the selection of thefirst selectable image portion includes the processor selecting thefirst selectable image portion based on the first selectable imageportion being associated with the first DTC.

EEE 7 is the method of any one of EEEs 4 to 6, wherein the imageincludes a three dimensional wire frame image.

EEE 8 is the method of any one of EEEs 4 to 7, wherein the image depictsa generic vehicle, and the image is further associated with at least asecond vehicle model identifiable from attributes of a second vehiclethat is not a vehicle of the vehicle model associated with the firstvehicle.

EEE 9 is the method of any one of EEEs 4 to 8, wherein outputting theimage associated with the vehicle model includes outputting, by the oneor more processors, a first subset of the multiple selectable imageportions, the method further comprising: receiving, by the one or moreprocessors while the first subset of the multiple selectable imageportions is output to the display, an input to change the image; andoutputting, by the one or more processors in response to receiving theinput to change the image, a second subset of the multiple selectableimage portions to the display.

EEE 10 is the method of any one of EEEs 1 to 9, further comprising:receiving, by the one or more processors, one or more attributes of thefirst vehicle from a vehicle data message transmitted by an ECU withinthe first vehicle; and wherein determining the vehicle model associatedwith the first vehicle includes determining, by the one or moreprocessors, the one or more attributes matches a stored attribute mappedto the vehicle model.

EEE 11 is the method of any one of EEEs 1 to 10, further comprising:outputting, by the one or more processors to a display, one or more ofthe following: a DTC selector, a damaged portion selector, or a vehicleadjustment selector; and displaying, by the display, one or more of thefollowing: the DTC selector, the damaged portion selector, or thevehicle adjustment selector.

EEE 12 is the method of EEE 11, further comprising: receiving, by theone or more processors, an input indicative of the DTC selector beingselected; outputting, by the one or more processors in response toreceiving the input, DTC data, wherein the DTC data includes DTC dataregarding the first DTC set within the first ECU in the first vehicle;and displaying, by the display, the DTC data.

EEE 13 is the method of EEE 11 or EEE 12, further comprising: receiving,by the one or more processors, an input indicative of the collisiondamage selector being selected; outputting, by the one or moreprocessors in response to receiving the input, an image associated withthe first vehicle model, wherein the image is divided into multipleselectable image portions, wherein each selectable image portioncorresponds to a different damaged portion of vehicles of the firstvehicle model, and wherein a first selectable image portion correspondsto the first damaged portion; and displaying, by the display, the imageassociated with the first vehicle model.

EEE 14 is the method of any one of EEEs 11 to 13, further comprising:receiving, by the one or more processors, a first input indicative ofthe vehicle adjustment selector being selected; outputting, by the oneor more processors in response to receiving the first input, (a) vehicleadjustment information regarding a vehicle adjustment, and (b) a secondvehicle adjustment selector; and displaying, by the display, the vehicleadjustment information and the second vehicle adjustment selector.

EEE 15 is the method of EEE 14, further comprising: receiving, by theone or more processors, a second input indicative of the second vehicleadjustment selector being selected; and outputting, by the one or moreprocessors in response to receiving the second input, a signal orcommunication to perform a vehicle adjustment corresponding to thesecond vehicle adjustment selector, wherein the vehicle adjustmentincludes (a) programming a vehicle component in the first vehicle, (b)initializing a vehicle component in the first vehicle, (c) calibrating avehicle component in the first vehicle, or (d) resetting a vehiclecomponent in the first vehicle.

EEE 16 is the method of any one of EEEs 1 to 15, further comprising:determining, by the one or more processors, a first parameter from thefirst vehicle indicative of the first DTC setting within the first ECU;determining, by the one or more processors, a second parameterpertaining to a current operating state of the first vehicle; whereindetermining the first DTC is collision-related is further based upon adifference in the first parameter and the second parameter being withina threshold range, and wherein the first parameter and the secondparameter are both indicative of a distance the first vehicle has beendriven or a number of driving cycles.

EEE 17 is the method of any one of EEEs 1 to 16, further comprising:determining, by the one or more processors, a second DTC set within thefirst ECU or a second ECU in the first vehicle; and determining, by theone or more processors, the second DTC is non-collision-related, whereinthe collision report indicates the second DTC is non-collision-related.

EEE 18 is the method of any one of EEEs 1 to 17, further comprising:receiving, by the one or more processors, at least a portion of anestimate or repair order pertaining to the first vehicle and thecollision, wherein determining the first damaged portion of the firstvehicle includes the one or more processors determining the firstdamaged portion from the at least a portion of the estimate or repairorder.

EEE 19 is the method of any one of EEEs 1 to 18, further comprising:receiving, by the one or more processors, an image of the first damagedportion of the first vehicle; and comparing, by the one or moreprocessors, the image of the first damaged portion of the first vehicleto a stored image showing an undamaged portion of a vehicle associatedwith the vehicle model, wherein determining the first damaged portion ofthe first vehicle includes the one or more processors determining thefirst damaged portion of the first vehicle pertains to the undamagedportion shown in the stored image.

EEE 20 is the method of any one of EEEs 1 to 19, further comprising:performing, by the one or more processors, a pre-repair scan of thefirst vehicle to determine which diagnostic trouble codes are set in thefirst vehicle prior to the first damaged portion of the first vehiclebeing repaired; and performing, by the one or more processors, apost-repair scan of the first vehicle to determine which diagnostictrouble codes are set in the first vehicle after the first damagedportion of the first vehicle is repaired.

EEE 21 is the method of any one of EEEs 1 to 20, wherein the collisionreport includes time data indicative of when the first DTC was set withrespect to a time when the collision occurred.

EEE 22 is the method of any one of EEEs 1 to 21, further comprising:determining, by the one or more processors, a warning regardingrepairing the first vehicle, wherein determining the warning includesthe one or more processors determining the warning is mapped to thereference vehicle portion; outputting, by the one or more processors toa display, the warning; and displaying, by the display, the warning.

EEE 23 is the method of any one of EEEs 1 to 22, wherein the componentincludes a wire or a fiber optical cable.

EEE 24 is the method of any one of EEEs 1 to 23, further comprising:determining, by the one or more processors, a possible related collisiondamage to the first vehicle; and augmenting, by the one or moreprocessors, the collision report based on the possible related collisiondamage to the first vehicle.

EEE 25 is the method of EEE 24, further comprising; displaying, by thedisplay, an identifier of the possible related collision damage to thefirst vehicle; and receiving, by the one or more processors, a selectionof the possible related collision damage, wherein augmenting thecollision report is further based on the selection of the possiblerelated collision damage.

EEE 26 is the method of any one of EEEs 1 to 25, wherein the vehicle isa first vehicle, the method further comprising: determining, by the oneor more processors, an amount of deflection at the first damaged portionof the first vehicle, determining, by the one or more processors,possible related collision damage based on the amount of deflection atthe first damaged portion of the first vehicle and actual damage to asecond vehicle associated with an amount of deflection at a damagedportion of the second vehicle, wherein the damaged portion of the secondvehicle matches the first damaged portion of the first vehicle; anddisplaying, by the display, an indication of the possible relatedcollision damage.

EEE 27 is a computing system comprising: a computer-readable memoryhaving stored thereon a reference vehicle portion associated with both acomponent attributable to setting a first diagnostic trouble code (DTC)and a vehicle model associated with a first vehicle; and one or moreprocessors configured to refer to the computer-readable memory andprogrammed to: (1) determine the vehicle model associated with the firstvehicle; (2) determine the first DTC set within a first electroniccontrol unit (ECU) in the first vehicle; (3) determine, a first damagedportion of the first vehicle, wherein the first damaged portionindicates where the first vehicle was damaged by a collision; (4)determine the first DTC is collision-related, wherein determining thefirst DTC is collision-related includes determining the first damagedportion of the first vehicle matches the reference vehicle portionassociated with both the component attributable to setting the first DTCand the vehicle model associated with the first vehicle; and (5) outputa collision report that indicates the first DTC is collision-related.

EEE 28 is the computing system of EEE 27, further comprising: a vehiclecommunications transceiver configured for being operatively connected tothe first vehicle.

EEE 29 is the computing system of EEE 27 or EEE 28, further comprising:a network transceiver configured for being operatively connected to ascanner coupled to the first vehicle.

EEE 30 is the computing system of EEE 27 or EEE 28, further comprising:a network transceiver configured for being operatively connected to aserver and/or a network computing system.

EEE 31 is the computing system of one of EEE 27 to EEE 30, furthercomprising: a display operatively connected to the one or moreprocessors, wherein the display is configured to display a displayscreen output by the one or more processors.

EEE 32 is the computing system of one of EEE 27 to EEE 31, furthercomprising: a keypad.

EEE 33 is the computing system of one of EEE 27 to EEE 32, furthercomprising: a capture device, wherein the capture device is configuredto generate data based on objects in proximity to the computing systemand/or signals from which that data can be generated.

EEE 34 is the computing system of one of EEE 27 to EEE 33, furthercomprising: an audio device.

EEE 35 is the computing system of one of EEE 27 to EEE 34, furthercomprising: a power supply and/or housing.

EEE 36 is a computer readable memory having stored thereon instructionsexecutable by one or more processors to cause a computing system toperform functions comprising: (1) determining a vehicle model associatedwith a first vehicle; (2) determining a first diagnostic trouble code(DTC) set within a first electronic control unit (ECU) in the firstvehicle; (3) determining a first damaged portion of the first vehicle,wherein the first damaged portion indicates where the first vehicle wasdamaged by a collision; (4) determining the first DTC iscollision-related, wherein determining the first DTC iscollision-related includes determining, by the one or more processors,the first damaged portion of the first vehicle matches a referencevehicle portion associated with both a component attributable to settingthe first DTC and the vehicle model associated with the first vehicle;and (5) outputting a collision report that indicates the first DTC iscollision-related.

EEE 37 is a system comprising: one or more processors, a non-transitorycomputer readable medium, and program instructions stored on thenon-transitory computer readable medium and executable by the one ormore processors to cause a set of functions to be performed, the set offunctions comprising a method in accordance with any one of EEEs 1 to26.

EEE 38 is the computing system of EEE 37, further comprising: a vehiclecommunications transceiver configured for being operatively connected tothe first vehicle.

EEE 39 is the computing system of EEE 37 or EEE 38, further comprising:a network transceiver configured for being operatively connected to ascanner coupled to the first vehicle.

EEE 40 is the computing system of EEE 37 or EEE 38, further comprising:a network transceiver configured for being operatively connected to aserver and/or a network computing system.

EEE 41 is the computing system of one of EEE 37 to EEE 40, furthercomprising: a display operatively connected to the one or moreprocessors, wherein the display is configured to display a displayscreen output by the one or more processors.

EEE 42 is the computing system of one of EEE 37 to EEE 41, furthercomprising: a keypad.

EEE 43 is the computing system of one of EEE 37 to EEE 42, furthercomprising: a capture device, wherein the capture device is configuredto generate data based on objects in proximity to the computing systemand/or signals from which that data can be generated.

EEE 44 is the computing system of one of EEE 37 to EEE 43, furthercomprising: an audio device.

EEE 45 is the computing system of one of EEE 37 to EEE 44, furthercomprising: a power supply and/or housing.

EEE 46 is a computer readable medium storing program instructions, thatwhen executed by one or more processors, cause a set functions to beperformed, the set of functions comprising a method in accordance withany one of EEEs 1 to 26.

We claim:
 1. A computing system comprising: one or more processors; a non-transitory computer-readable memory; and program instructions stored on the non-transitory computer-readable memory and executable by the one or more processors to: determine a vehicle model associated with a first vehicle; determine a first diagnostic trouble code set within a first electronic control unit in the first vehicle; determine a first damaged portion of the first vehicle, wherein the first damaged portion indicates where the first vehicle was damaged by a collision; determine that the first diagnostic trouble code is collision-related, wherein determining the first diagnostic trouble code is collision-related includes determining that the first damaged portion of the first vehicle matches a reference vehicle portion associated with both a component attributable to setting the first diagnostic trouble code and the vehicle model associated with the first vehicle; and output a collision report that indicates the first diagnostic trouble code is collision-related.
 2. The computing system according to claim 1, further comprising: a vehicle communications transceiver configured to operatively connect to the first vehicle wirelessly and/or via a wiring harness and is configured to transmit, to the first vehicle, a vehicle data message including a request for diagnostic trouble codes set in the first vehicle.
 3. The computing system according to claim 2, wherein: the vehicle communications transceiver is configured to receive a response to the request for diagnostic trouble codes set in the first vehicle, the response includes time data indicative of when the first diagnostic trouble code was set with respect to a time when the collision occurred, and the collision report includes the time data indicative of when the first diagnostic trouble code was set with respect to a time when the collision occurred.
 4. The computing system according to claim 1, further comprising: a network transceiver configured to: operatively connect the computing system to a server, and receive, from the server, computer-readable data indicative of the reference vehicle portion associated with both the component attributable to setting the diagnostic trouble code and the vehicle model associated with the first vehicle.
 5. The computing system according to claim 1, wherein the non-transitory computer-readable memory contains computer-readable data indicative of the reference vehicle portion associated with both the component attributable to setting the diagnostic trouble code and the vehicle model associated with the first vehicle.
 6. The computing system according to claim 1, further comprising: a display connected to the one or more processors, wherein the display is configured to display the collision report that indicates the first diagnostic trouble code is collision-related.
 7. The computing system according to claim 6, wherein: the collision report includes a vehicle adjustment selector applicable to the first vehicle, and the program instructions are executable by the one or more processors to: receive a selection of the vehicle adjustment selector; and transmit, to the first vehicle in response to receiving the selection of the vehicle adjustment selector, one or more vehicle data messages that cause the first vehicle to perform an adjustment to the first vehicle, and optionally, the adjustment to the first vehicle includes: calibrating a component on the first vehicle, programming the component on the first vehicle, resetting the component on the first vehicle, or initializing the component on the first vehicle.
 8. The computing system according to claim 1, further comprising: a display connected to the one or more processors, wherein: the program instructions are executable by the one or more processors to output, onto the display, an image associated with the vehicle model, the image is divided into multiple selectable image portions, a first selectable image portion of the multiple selectable image portions corresponds to a first portion of the vehicle model, the program instructions are executable by the one or more processors to receive a selection of the first selectable image portion, and the program instructions executable by the one or more processors to determine the first damaged portion of the first vehicle use the selection of the first selectable image portion to determine the first damaged portion of the first vehicle.
 9. The computing system according to claim 8, wherein the program instructions executable by the one or more processors to receive the selection of the first selectable image portion include program instructions executable by the one or more processors to determine that a portion of the display at which the first selectable image portion is displayed is touched.
 10. The computing system according to claim 8, wherein the program instructions executable by the one or more processors to receive the selection of the first selectable image portion include program instructions executable by the one or more processors to select the first selectable image portion based on the first selectable image portion being associated with the first diagnostic trouble code.
 11. The computing system according to claim 8, wherein: the image depicts a generic vehicle, and the image is further associated with at least a second vehicle model identifiable from attributes of a second vehicle that is not a vehicle of the vehicle model associated with the first vehicle, and optionally, the image includes a three dimensional wire frame image.
 12. The computing system according to claim 8, wherein: the program instructions executable by the one or more processors to output the image associated with the vehicle model include program instructions executable by the one or more processors to output, onto the display, a first subset of the multiple selectable image portions, the program instructions are executable by the one or more processors to: receive, while the first subset of the multiple selectable image portions is output onto the display, an input to change the image associated with the vehicle model; and output, onto the display in response to receipt of the input to change the image, a second subset of the multiple selectable image portions.
 13. The computing system according to claim 1, wherein: the program instructions are executable by the one or more processors to: receive one or more attributes of the first vehicle from a vehicle data message transmitted by a particular electronic control unit within the first vehicle, and the program instructions executable by the one or more processors to determine the vehicle model associated with the first vehicle include program instructions that are executable by the one or more processors to determine that the one or more attributes match one or more stored attributes mapped to the vehicle model.
 14. The computing system according to claim 1, further comprising: a display connected to the one or more processors, wherein the program instructions are executable by the one or more processors to: output a diagnostic trouble code selector onto the display, receive an input indicative of the diagnostic trouble code selector being selected, and output, onto the display in response to receiving the input, diagnostic trouble code data, and wherein the diagnostic trouble code data includes data regarding the first diagnostic trouble code set within the first diagnostic trouble code in the first vehicle.
 15. The computing system according to claim 1, further comprising: a display connected to the one or more processors, wherein the program instructions are executable by the one or more processors to: output a damaged portion selector onto the display, receive an input indicative of the damaged portion selector being selected, and output, onto the display in response to receiving the input, an image associated with the vehicle model, and wherein: the image is divided into multiple selectable image portions, each selectable image portion corresponds to a different damaged portion of vehicles of the vehicle model, and a first selectable image portion corresponds to the first damaged portion.
 16. The computing system according to claim 1, further comprising: a display connected to the one or more processors, wherein the program instructions are executable by the one or more processors to: output a vehicle adjustment selector onto the display, receive a first input indicative of the vehicle adjustment selector being selected, and output, onto the display in response to receiving the first input: vehicle adjustment information regarding a first vehicle adjustment, and a second vehicle adjustment selector.
 17. The computing system according to claim 16, wherein: the program instructions are executable by the one or more processors to: receive a second input indicative of the second vehicle adjustment selector being selected, and output, in response to receiving the second input, a signal or communication to perform a second vehicle adjustment corresponding to the second vehicle adjustment selector, and one or both of the first vehicle adjustment or the second vehicle adjustment includes: programming a vehicle component in the first vehicle, initializing a vehicle component in the first vehicle, calibrating a vehicle component in the first vehicle, or resetting a vehicle component in the first vehicle.
 18. The computing system according to claim 1, wherein: the program instructions are executable by the one or more processors to: determine a first parameter from the first vehicle indicative of the first diagnostic trouble code setting within the first electronic control unit, determine a second parameter pertaining to a current operating state of the first vehicle, the program instructions executable by the one or more processors to determine that the first diagnostic trouble code is collision-related include program instructions that determine the first diagnostic trouble code is collision-related based upon a difference in the first parameter and the second parameter being within a threshold range, and the first parameter and the second parameter are both indicative of a distance the first vehicle has been driven or a number of driving cycles.
 19. The computing system according to claim 1, wherein: the program instructions are executable by the one or more processors to: determine a second diagnostic trouble code set within the first electronic control unit or within a second electronic control unit in the first vehicle; and determine the second diagnostic trouble code is non-collision-related, and the collision report indicates the second diagnostic trouble code is non-collision-related.
 20. The computing system according to claim 1, wherein: the program instructions are executable by the one or more processors to: receive at least a portion of an estimate or repair order pertaining to the first vehicle and the collision, and the program instructions executable by the one or more processors to determine the first damaged portion of the first vehicle include program instructions executable by the one or more processors to determine the first damaged portion from the at least a portion of the estimate or repair order.
 21. The computing system according to claim 1, wherein: the program instructions are executable by the one or more processors to: receive an image of the first damaged portion of the first vehicle, compare the image of the first damaged portion of the first vehicle to a stored image showing an undamaged portion of a vehicle associated with the vehicle model, and the program instructions executable by the one or more processors to determine the first damaged portion of the first vehicle include program instructions that are executable by the one or more processors to determine the first damaged portion of the first vehicle pertains to the undamaged portion shown in the stored image.
 22. The computing system according to claim 1, wherein: the program instructions are executable by the one or more processors to: perform a pre-repair scan of the first vehicle to determine which diagnostic trouble codes are set in the first vehicle prior to the first damaged portion of the first vehicle being repaired; and perform a post-repair scan of the first vehicle to determine which diagnostic trouble codes are set in the first vehicle after the first damaged portion of the first vehicle is repaired.
 23. The computing system according to claim 1, further comprising: a display connected to the one or more processors, wherein: the program instructions are executable by the one or more processors to determine a warning regarding repairing the first vehicle based on the warning being mapped to the reference vehicle portion, and to output the warning to the display, and the display is configured to display the warning.
 24. The computing system according to claim 1, wherein: the program instructions are executable by the one or more processors to: determine a possible related collision damage to the first vehicle; and augment the collision report based on the possible related collision damage to the first vehicle.
 25. The computing system according to claim 24, wherein: the program instructions executable by the one or more processors to determine the possible related collision damage to the first vehicle include program instructions executable by the one or more processors to: determine crash and damage data corresponding to a vehicle similar to the first vehicle has one or more parameters of crash data that match or are within a threshold of one or more similar parameters of crash data of the crash and damage data corresponding to the first vehicle, and determine damage data of the crash and damage data corresponding to the vehicle similar to the first vehicle indicates one or more components not included within damage data of the crash and damage data corresponding to the first vehicle, and the possible related collision damage to the first vehicle is indicative of the one or more components not included within damage data of the crash and damage data corresponding to the first vehicle.
 26. The computing system according to claim 24, further comprising: a display connected to the one or more processors, wherein: the program instructions are executable by the one or more processors to: output onto the display an identifier of the possible related collision damage to the first vehicle; and receive a selection of the possible related collision damage to the first vehicle, and the program instructions to augment the collision report include program instructions to augment the collision report further based on the selection of the possible related collision damage to the first vehicle.
 27. The computing system according to claim 1, further comprising: a display connected to the one or more processors, wherein the program instructions are executable by the one or more processors to: determine an amount of deflection at the first damaged portion of the first vehicle, determine possible related collision damage based on the amount of deflection at the first damaged portion of the first vehicle and actual damage to a second vehicle associated with an amount of deflection at a damaged portion of the second vehicle, and output onto the display an indication of the possible related collision damage, and wherein the damaged portion of the second vehicle matches the first damaged portion of the first vehicle.
 28. The computing system according to claim 27, further comprising: one or more laser transmitters and receivers, wherein the program instructions to determine the amount of deflection at the first damaged portion of the first vehicle cause the one or more processors to: make measurements using the one or more lasers and transmitter to generate an outline of the first vehicle; and determine one or more differences in portions of the outline of the first vehicle and portions of an outline of a similar vehicle, and wherein the portions of the outline of the first vehicle and the portions of an outline of a similar vehicle correspond to similar portions of the first vehicle and the similar vehicle.
 29. The computing system according to claim 1, wherein the program instructions executable by the one or more processors to determine that the first diagnostic trouble code is collision-related include program instructions executable by the one or more processors to: determine multiple parameter identifiers associated with the first diagnostic trouble code; normalize first parameter values from the first vehicle that correspond to a particular parameter identifier of the multiple parameter identifiers; normalize second parameter values from the first vehicle that correspond to other parameter identifiers of the multiple parameter identifiers; and determine that the first normalized parameter values deviate from a mean operating parameter value of the particular parameter identifier when the first vehicle is not malfunctioning at a rate greater than the second normalized parameter values deviate from mean operating parameter values of the other parameter identifiers when the first vehicle is not malfunctioning.
 30. The computing system according to claim 1, further comprising: a capture device configured to generate a captured image of the first vehicle; and a display connected to the one or more processors, wherein the program instructions executable by the one or more processors to determine the first damaged portion of the first vehicle include program instructions executable by the one or more processors to: output, onto the display, the captured image of the first vehicle and an image of an undamaged vehicle corresponding to a year, make, and model of the first vehicle, wherein one of the captured image of the first vehicle or the image of undamaged vehicle is overlaid upon another of the captured image of the first vehicle or the image of undamaged vehicle, determine a difference in first edge lines indicative of the first vehicle shown in the captured image of the first vehicle and second edge lines indicative of a vehicle shown in the image of undamaged vehicle at corresponding portions of the first vehicle shown in the captured image of the first vehicle and the vehicle shown in the image of undamaged vehicle.
 31. The computing system according to claim 30, wherein the program instructions executable by the one or more processors to determine the first damaged portion of the first vehicle include program instructions executable by the one or more processors to adjust a scale of one or more of the captured image of the first vehicle or the image of undamaged vehicle.
 32. The computing system according to claim 1, further comprising: a display connected to the one or more processors, wherein the program instructions executable by the one or more processors to determine the first damaged portion of the first vehicle include program instructions executable by the one or more processors to: output one or more measurement fields configured for entry of a gap measurement, wherein the gap measurement indicates a distance between two adjacent vehicle body components, and determine that a particular gap measurement entered into a particular measurement field is greater than a gap measurement between two corresponding adjacent vehicle body components on a reference vehicle corresponding to a year, make, and model that match a year, make, and model corresponding to the first vehicle. 